Root cause analysis and systematic fix. Quick root cause location, then 6-phase systematic loop for bug fixes. Use when errors, crashes, regressions, test failures, anomalous behavior, or the user says 'used to work'. Trigger words: debug, 排查, 报错, 崩溃, 不工作, regression, 以前是好的, broken after update.
Build a throwaway prototype to answer one design question with disposable code. Two branches: a tiny interactive terminal app for logic/state-model questions, or several radically different UI variations toggleable from one route. Use when a design doubt is easier to resolve by running code than by reasoning on paper — state machine edges, data-model expressiveness, or what a page should look like. Trigger words: prototype, 原型, 试一下, spike, 验证一下, 看看效果, 跑起来看看, 有没有更简单的方式, 这个状态机对不对, 这个数据模型能表达吗.
Implement a piece of work based on a PRD or set of issues. Orchestrates /tdd at pre-agreed seams, runs typechecking and tests regularly, dispatches /review at the end, and commits the completed work to the current branch.
Periodically review and improve code architecture. Scan existing PRDs, find deepening opportunities and design debt based on domain language and decision records. Use for regular code health checks or proactive design debt cleanup. Trigger words: architecture, improve-architecture, 重构, 清理, 债务, 架构审查.
Parallel three-perspective code review via sub-agent orchestration. Dispatches Test Review, Code Review, and Impact Review sub-agents in parallel — each independently re-reads all shared context. Merges reports, highlights contradictions for human adjudication. Use after task completion, before merge, or before release. Trigger words: review, check, 把关, 发布前, 完成开发, 验收, code review.
Break a plan into executable Issues using vertical slices. Accepts an existing PRD or a direct feature description. Use when the user wants to convert a plan to Issues, create implementation tickets, or decompose work into subtasks. Trigger words: breakdown, story, 拆分, Issues, tasks, subtasks, decompose.
Brainstorm and converge on solutions — diverge on possibilities, converge to a decision-complete plan, generate an initial PRD. Use when requirements are unclear, multiple implementation paths exist, or the user describes a new feature, architecture decision, or complex task. Trigger words: brainstorm, 构思, plan, how should I, design approach, feasibility, 技术方案.
Challenge plans by extracting every open decision from the PRD and resolving them one by one — skip none. Interview relentlessly about every aspect of the plan, walking down each branch of the design tree until shared understanding is reached. Use after think to validate the plan against the existing domain model, sharpen terminology, update CONTEXT.md and ADRs. Trigger words: challenge, 细化和验证, deep dive, question the plan, grill, validate plan, 这个方案行不行, 审查设计, find holes, stress test.