spec-plan
把需求或明确目标转成结构化实施计划，定义 HOW。
基本信息
| 字段 | 内容 |
|---|---|
| Skill | spec-plan |
| 类型 | workflow command |
| 研发链路位置 | Plan |
| 入口 | /spec:plan / $spec-plan |
| Source | skills/spec-plan/SKILL.md |
描述
Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', 'plan a trip', 'create a study plan', or when a brainstorm/requirements document is ready for planning. Use for plan deepening when the user says 'deepen the plan', 'deepen my plan', 'deepening pass', or uses 'deepen' in reference to a plan. For exploratory or ambiguous requests where the user is unsure what to do, prefer spec-brainstorm first.
何时使用
- WHAT 基本清楚但 HOW 未定。
- 需要文件边界、技术路线、风险、测试场景和 sequencing。
- 已有 requirements 文档需要进入实施设计。
工作步骤
- 读取 requirements、standards、graph facts、相邻代码和测试模式。
- 确定 HOW：技术路线、文件边界、依赖顺序、风险和验证面。
- 把未知项分类为 planning blocker 或 implementation-time unknown。
- 输出可执行但不写代码的实施计划。
输出
- implementation plan、requirements trace、file list、test scenarios 和 verification plan。
- 需要 task pack 时，交给 spec-write-tasks；可直接实现时，交给 spec-work。
Agent 调度
- 需要额外 grounding 时使用 repo research、git history、framework docs 或 best-practices agents。
- 计划质量可交给 doc-review personas 复核。
边界
- 不执行代码。
- 产品 blocker 未解决时应回到 brainstorm 或明确假设。