Propose a Conventional Commit message for the staged changes, then commit only after confirmation.
Creates an implementation plan from a PRD or a task description. Researches codebase context, clarifies ambiguities, and outputs a phased plan with vertical slices and acceptance criteria. Use when the user wants to plan a feature, break down a PRD, create an implementation plan, or mentions "tracer bullets".
Creates a PRD through structured clarification, codebase exploration, and module design, then saves it as a local Markdown file. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
Dispatches multiple subagents in parallel for 2+ confirmed-independent, each-substantial failures or investigation targets that share no state or sequential dependency. Use when the work splits cleanly and each part is big enough to justify a separate agent.
Decides how to integrate a finished branch โ merge, pull request, keep, or discard โ once tests pass. Use when implementation work on a branch is complete and you need to decide what happens to it next.
Acts on code-review feedback (from a human, a PR comment, or an AI reviewer) by verifying each item against the codebase before implementing, and asking when items are unclear. Use when receiving code review comments, PR feedback, or suggestions from another reviewer โ before implementing any of them.
Investigates a bug, test failure, or unexpected behavior root-cause-first before proposing a fix. Use when a test fails, an error shows up in logs or CI, or something behaves unexpectedly and the next step would otherwise be guessing at a patch.
Creates or reuses an isolated git worktree for feature work, a risky refactor, or unattended agent runs. Use when starting work that shouldn't touch the current checkout, before executing a multi-step plan, or when running an agent unattended and it needs its own branch and directory.