Run Codex pre-implementation research on a task. Use when the user invokes /hyperclaude:hyper-research, or when starting a non-trivial implementation and you want Codex's…
Apply test-driven development discipline when implementing code changes. Use when about to write or modify behavior-bearing code (functions, modules, business logic).
Sync documentation to reflect recent code changes. Use when the user invokes /hyperclaude:hyper-docs-sync or after implementing changes that affect documented behavior (API…
Run Codex critique on an implementation plan. Use when the user invokes /hyperclaude:hyper-plan-review, after Claude has produced a plan that should be sanity-checked before…
Generate an ordered, bite-sized plan via the planner agent and save it to .hyperclaude/plans/. Use when the user invokes /hyperclaude:hyper-plan, or when about to start a…
Execute a plan task-by-task using fresh subagents, with spec compliance + code quality reviews between tasks.
Run Codex accuracy review on documentation. Use when the user invokes /hyperclaude:hyper-docs-review or after the documenter agent edits docs.
Run Codex's native code-review on the current branch, working tree, or a specific commit. Use when the user invokes /hyperclaude:hyper-code-review, or after producing code changes…
Apply systematic debugging discipline when a test fails, code throws, or behavior diverges from expectation. Use the moment something is unexpectedly broken.