协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
review【开发与工程】Use before merge, after subagents, or for spec/plan review.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
If topology=multi-module (triage announcement or coordinator spec/plan declaration), read ../references/multi-module.md. Review each module diff in its owning repository first, then review the workspace as one change set. Block missing repositories, copied or divergent shared contracts, undeclared cross-module edits, overlapping writers, incomplete local acceptance, or integration results that do not identify the tested workspace combination.
Check in order:
convention, idiomatic for the stack? (see ../references/quality.md)contract covers full public surface? Env vars/config/error modes documented? README commands runnable? Living docs honor North Star (atemporal ground truth, modular specs; see ../references/quality.md)?For spec/plan reviews, also block unresolved implementation notes, plan assumptions absent from spec, vague acceptance, or premature [parallel].
Report:
BLOCK: <must fix>
FIX: <should fix>
NIT: <optional>
BLOCKs resolved before merge. FIX resolved or explicitly deferred with reason.