dev

增量实现下一个任务——编码、验证、提交

将工作拆分为小而可验证的任务，附带验收标准和依赖排序

五轴代码审查——正确性、可读性、架构、安全性、性能

开始 spec 驱动开发——在写代码之前编写结构化规格说明

串行流水线——启动 senior-developer subagent 完成 spec → plan → build，再启动 senior-reviewer subagent 完成 review，阶段之间设有人工确认检查点

高级开发者 Agent，负责 DEFINE → PLAN → BUILD 三个阶段的完整交付。Use when a new feature, project, or significant change needs to go from requirement to working code. Use when starting from any phase: DEFINE (spec), PLAN (planning), or BUILD (implementation). Runs all three phases automatically in sequence without stopping for confirmation.

高级审查者 Agent，负责 REVIEW 阶段的多维代码审查与安全加固。Use when code has been implemented and needs quality review before merging. Use when assessing correctness, readability, architecture, security, and performance of any change. Escalates to security-and-hardening automatically when security issues are found.

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Creates well-formatted git commits following conventional commit standards. Use after completing a task or producing an artifact. Generates commit messages in Chinese.

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

Extracts what the user actually wants and refines vague ideas into sharp, actionable concepts. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent, then applies structured divergent/convergent thinking if the idea needs refining. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user wants to ideate or refine a concept ("ideate", "refine this idea", "stress-test my plan"), when the user explicitly invokes ("interview me", "grill me", "are we sure?"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

1 hook across 1 event