YSAA1

brainstorm

用于把模糊需求收敛成用户批准过的 Spec。触发条件：目标、边界、方案取舍、成功标准或验证策略还没收敛，或用户说先讨论/先落 Spec。不要在已有完整 Spec、直接小补丁或只需事实回答时使用；Spec 批准后交给 plan。

cleanup

用于在完成、阻塞、放弃或交接前对齐 docs、generated artifacts、recovery surface 和知识状态。触发条件：用户说收尾/同步文档/整理状态，或 verify 后需要 closure。不要把 cleanup 当代码重构或行为改动入口；行为变化回 implement/plan。

diagnose

用于把 build/test/lint/typecheck/CI 或运行时失败诊断成可复现 root cause。触发条件：命令红、行为坏、flaky 或本地/CI 不一致且根因未知。不要在 RED->GREEN 的已知失败或根因已清楚时使用；修复前必须先复现和验证单一假设。

Use this helper to discover reusable agent skills for a clear task or capability gap. Trigger it when the user asks how to do X, find a skill, or extend agent capabilities. Do not install or adopt a skill just because it is related; project adoption belongs to harness-builder.

harness-builder

Project-level Harness Builder for recommending, designing, or repairing the project workbench and recovery surface: AGENTS.md/CLAUDE.md, project map, project iron laws, verification entry point, reusable skills, justified hooks, subagents, MCP policy, Capability Recommendation, and anti-entropy guardrails. Trigger when the user says harness builder, bootstrap, initialize, onboard, build harness, prepare workbench, create project rules, find reusable skills, recommend capabilities, or repair recovery surface.

implement

用于在一个 scoped active slice 上做最小代码或文档改动。触发条件：用户请求/Spec/Executable Plan 已清楚，工作面和验证路径足够明确。不要在需求、active slice、根因或工作面不清时使用；局部检查只是反馈，ready 只能交给 verify。

plan

用于把已批准 Spec 或足够明确的非平凡请求转成 Executable Plan。触发条件：需要 active slice、planning surface、验证路径、能力缺口或 commit unit。不要在需求/验证策略不清时使用；先回 brainstorm。项目工作面不清时转 harness-builder。

Code & Development Listed

review

用于对稳定 diff 做 scope、correctness、docs、entropy 和 risk 的结构性评审。触发条件：implement/diagnose 后准备进入 ready 证明，或用户要求 review/sanity check。不要在 WIP、失败未解释或只需要 fresh evidence 时使用；review 不能声明 ready。