メニュー
Use when the autopilot orchestrator main thread reaches Phase 2 or Phase 3 and must dispatch the mechanical OpenSpec change creation and Fast-Forward artifact generation as background tasks against the prepared requirements bundle.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user invokes /slim-task or requests structured multi-phase task execution (structured task, SOP execution, parallel sub-agent dispatch) with blind-audit quality review.
Use when autopilot orchestrator enters Phase 1 to understand requirements, drive multi-round clarification, and produce the structured requirement packet checkpoint.
Use when the autopilot orchestrator enters Phase 5 after Phase 4 test case design has been approved and is about to choose an implementation path (parallel, serial, or TDD) and dispatch implementation work.
Use when the autopilot orchestrator reaches Phase 7 after Phase 6 tri-path reports are available and must finalize the delivery by collecting summaries, extracting knowledge, previewing Allure, and evaluating archive readiness.
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", "figma to code", "figma 转代码", "figma 还原", "实现设计稿", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`. For full-screen design generation in Figma, use `figma-generate-design`.
Use when the autopilot orchestrator main thread is about to dispatch a phase-specific sub-agent via the Task tool and needs the JSON envelope contract, explicit path injection, and parameterized prompt templates. Not for direct user invocation; skip when the current context is not the autopilot orchestrator.
| name | autopilot-phase2-3-openspec |
| description | Use when the autopilot orchestrator main thread reaches Phase 2 or Phase 3 and must dispatch the mechanical OpenSpec change creation and Fast-Forward artifact generation as background tasks against the prepared requirements bundle. |
| user-invocable | false |
前置条件自检：本 Skill 仅在 autopilot 编排主线程中使用。如果当前上下文不是 autopilot 编排流程，请立即停止并忽略本 Skill。
Phase 2 和 Phase 3 均为机械性 OpenSpec 操作，共享同一 agent 和 model tier。本 Skill 描述两者在统一调度模板中的特殊行为。（下文 <name> 表示从需求推导出的 kebab-case change 名）
dispatch 的具体 prompt 构造逻辑保持在
autopilot-dispatch中。
Phase 2 与 Phase 3 共用以下派发约束：
config.phases.openspec.agent（默认 Plan）run_in_background: true：机械性操作不应占用主窗口上下文{"status": "ok", "summary": "...", "artifacts": [...]}
Hook 验证要求
status与summary必须存在，缺一即 block。
关键事实：openspec new change "<name>" 仅创建 .openspec.yaml 元数据文件（2 行：schema + created），不会自动生成 proposal.md 或 context 文件。子 Agent 必须自行编写所有制品文件。
子 Agent 必须执行的操作步骤：
Bash('openspec new change "<name>"') — 初始化 change 目录Bash('mkdir -p openspec/changes/<name>/context/phase-results/') — 创建 checkpoint 目录Bash('openspec instructions proposal --change "<name>"') — 获取 proposal 写作指引openspec/changes/<name>/proposal.md示例 summary：
{"status": "ok", "summary": "已创建 OpenSpec change: <name>，包含 proposal.md", "artifacts": ["openspec/changes/<name>/proposal.md"]}
关键事实：openspec CLI 不自动生成制品文件。openspec instructions <artifact> --change <name> 输出写作指引和模板，子 Agent 根据指引自行 Write 文件。
子 Agent 必须执行的操作步骤：
Bash('openspec instructions design --change "<name>"') — 获取 design 写作指引openspec/changes/<name>/design.mdBash('openspec instructions specs --change "<name>"') — 获取 specs 写作指引openspec/changes/<name>/specs/*.md（按 proposal 中声明的 capabilities 逐个创建）Bash('openspec instructions tasks --change "<name>"') — 获取 tasks 写作指引openspec/changes/<name>/tasks.md示例 summary：
{"status": "ok", "summary": "已生成 OpenSpec 制品: design/specs/tasks", "artifacts": ["openspec/changes/<name>/design.md", "openspec/changes/<name>/specs/", "openspec/changes/<name>/tasks.md"]}
check-predecessor-checkpoint.sh) 在 Task 派发时自动执行autopilot 内的 "Phase 2-3 联合调度快速路径" 章节定义了完整的 Fast-Step 0-9 流程