implementation-plan

Implementation Plan

Generate a structured implementation plan by delegating to superpowers:writing-plans, enriched with governance metadata.

Hard Gate

Prerequisite depends on project type:

• Type A: project-governor:state-design complete (state in phases_completed)
• Type B: project-governor:ui-design complete (ui in phases_completed)

Verify the appropriate artifact exists in docs/governor/ before proceeding.

PDCA Cycle

digraph plan_pdca {
    rankdir=LR;
    node [shape=box, style=filled];
    "P: Define plan scope" [fillcolor="#E3F2FD"];
    "D: Write implementation plan" [fillcolor="#E8F5E9"];
    "C: Gate-check plan" [fillcolor="#FFF3E0"];
    "A: Accept or rework" [fillcolor="#F3E5F5"];

    "P: Define plan scope" -> "D: Write implementation plan" -> "C: Gate-check plan" -> "A: Accept or rework";
    "C: Gate-check plan" -> "D: Write implementation plan" [label="fail", style=dashed];
}

Plan

• 目标：将所有设计产物转化为可执行的任务分解计划
• 输入：requirements + flow + state + (ui if B-type) specs
• 验收标准：每个需求有对应任务，每个任务有测试规格

Do

1. Load all design specs — Read from docs/governor/specs/, flows/, states/, and ui/ (if B-type). Assemble full design context. 语言要求：本次委托产出的所有文档必须使用中文撰写。如果被委托的 skill 输出英文内容，在保存为 artifact 之前必须翻译为中文。专业术语可在括号内保留英文原文。
2. Delegate to superpowers:writing-plans — Invoke writing-plans to create the implementation plan. Feed it the full design context. Let it drive:
   • Task decomposition into bite-sized (2-5 min) units
   • TDD test-first specification per task
   • Dependency ordering
   • Risk identification
3. Redirect plan output — Move the plan from docs/superpowers/plans/ to docs/governor/plans/YYYY-MM-DD-<project-name>-plan.md
4. Add governance header — Prepend to the plan:

   ---
   governance:
     cycle: <from project.yaml>
     requirements_spec: <filename>
     flow_spec: <filename>
     state_spec: <filename>
     ui_spec: <filename or "N/A for type A">
     plan_phase: plan
   ---
   

Check (阶段门禁)

Dispatch gate-checker agent against shared/gate-templates/plan-gate.md:

• Task list decomposed into bite-sized units
• Dependency order explicit, no circular deps
• Each task has test-first specification
• Every requirement covered by at least one task
• Every state transition implemented by some task
• Governance header with metadata present
• No placeholder content

Gate verdict → PASS / CONDITIONAL / FAIL

Act

• PASS: Append plan to phases_completed, set current_phase: plan. Write gate record. 更新 docs/governor/INDEX.md：更新当前阶段，追加产物记录行。
  • If auto: true in project.yaml: Automatically invoke project-governor:stage-gate.
  • If auto: false: Prompt: "Plan ready. Next: invoke project-governor:stage-gate for cross-phase consistency verification, or begin implementation with superpowers:subagent-driven-development"
• CONDITIONAL: Fix minor gaps inline, re-Check.
• FAIL: Return to Do — address gaps, re-Check.

Delegation Note

This skill delegates plan creation entirely to superpowers:writing-plans. We add:

• Cross-referencing to governance artifacts (traceability)
• Gate enforcement with PDCA loop
• Governance metadata header

Multi-Agent Acceleration

If the plan has independent task groups, offer the user:

• superpowers:subagent-driven-development — sequential with review
• superpowers:dispatching-parallel-agents — parallel execution for independent tasks

PDCA Context

Each phase is a self-contained PDCA loop. The implementation plan is the last design-phase artifact. Next: cross-phase stage gate verifies all artifacts are aligned.