tonywo2049

brainstorm

Use when a WhitePaper does not exist, needs a major rethink, or an approved WhitePaper needs a controlled semantic revision to its problem, goals, scope, harm order, invariants, or interpretation. Also covers a new idea, product concept, problem, opportunity, vague requirement, research request, feasibility study, brainstorm, or starting a direction. 需求澄清入口：新想法、产品构思、待解决问题、新机会、模糊需求、调研、可行性研究、脑暴/头脑风暴，以及已批准白皮书的问题、目标、范围、损害排序、不变量或理解需要受控语义修订；不改变语义的机械小修或纯闲聊不触发。

close-milestone

Use when every target-milestone task is closed and traceability is full to reconcile scope, run any still-required milestone regression/E2E, apply closure review gates, record owner review, and backfill ROADMAP plus any needed receiver handoff. 目标 Milestone 自有任务全部关账后做范围核对、仍必需的回归/E2E、关账审查门禁与负责人复核。

gmgn

Use first to route workflow-driven project work: new projects, product ideas, research, feature development, bug fixes, refactors, WhitePaper, project Decision, ROADMAP, PRD, requirements, design, task docs, coding delegation, launch, release, acceptance, or closure. 凡要按流程推进研发、调研、功能、修 bug、重构、写白皮书/项目决议/ROADMAP/PRD/需求/设计/任务、派活、上线发布、验收关账，或用户说按 GMGN/下一步做什么时使用。

release

Use after a candidate is already accepted to prepare or retry a version tag, deterministic package, checksum, GitHub/GitLab release, publication, deployment handoff, or local plugin update without repeating milestone closure. 已接受候选需要打 tag、生成发布包与校验和、创建或重试版本发布、交付部署或更新本地插件时使用；复用已绑定锚的验收证据，不重复里程碑关账。

roadmap

Use after owner approval of WhitePaper and the project Decision authority to create or maintain the project roadmap: outcome Milestones, deliverables, success signals, now/next/later horizons, relative priority, real dependencies, accepted-result links, and a curated Backlog. 白皮书和项目决议权威均已批准后，形成完整推荐候选并一次批准结果型里程碑、产出、成功信号、规划时域、相对优先级、真实依赖和受控 Backlog。

run-task

Use when an initiated Milestone has accepted Task.md rows: let one Commander compute ready work and prepare one Runner per Task, execute complete Card/Log and implementation candidates, review in each Runner, add risk-triggered verification, and let a Commander integrate the checked candidate. Milestone 已启动且 Task.md 已接受后，由 Commander 计算 ready set 并为每个 Task 准备一个 Runner；Runner 完成执行与审查，Commander 按门禁集成。

Web & Frontend Listed

write-design

Use after Requirement review to create or semantically revise the Design-stage bundle. Every creation or semantic revision first completes bounded external-solution research; root Design.md owns required implementation decisions, with module design and design/Contract.md only when needed. Requirement 已过审后创建或语义修订 Design Bundle；每次均先完成有边界的外部方案调研，再确定必要实现决定与按需的模块或跨单元接口权威。

write-goal

Use when an approved ROADMAP has an eligible `now`, `not-started` Milestone that needs one combined initiation and Goal approval, or for a controlled revision of an approved Goal. Define only the active boundary and qualitative Close outcomes in Goal.md as Requirement input. ROADMAP 已批且存在可启动的 `now` Milestone 时，形成 Goal 候选并用一次批准同时完成启动与 Goal 批准；也用于受控修订已批准 Goal。

write-requirement

Use after Goal.md is approved to analyze, clarify, create, or change functional/non-functional requirements, PRD/product requirements, requirement pool, user stories, acceptance criteria, or ACs in Requirement.md. Goal.md 已批准后写/补需求分析、PRD/产品需求文档、需求池、用户故事、验收标准/AC，或做受控需求变更。

write-task

Use after Design review to create or change Task.md: milestone task decomposition, AC-to-task mapping, dependencies, orchestration status, and pointers to per-card execution contracts. Design 已过审后拆任务、维护 AC→Task 映射、依赖、宏观执行状态及执行入口；单卡验证契约与执行细节不写入 Task.md。

write-decision

Use after WhitePaper approval and before ROADMAP, or whenever any current or proposed ruling should be recorded for downstream consumption, regardless of subject or Milestone scope. Create or revise root Decision.md as current authority and DecisionLog.md as descriptive accepted-change history. 白皮书批准后、ROADMAP 之前，或任意范围的现行或候选决议需要供下游消费时，创建或受控修订 Decision.md 与 DecisionLog.md。