gen-plan

name	gen-plan
description	Turn an approved spec or sufficiently clear Markdown draft into a concise, repo-grounded implementation plan with verifiable deliverables, scope, milestones, and checks. Use for generate a plan, implementation planning, 生成计划, or after gen-idea.

Gen Plan

Turn a settled design into an implementation plan. Do not brainstorm broadly, review externally, or implement the plan; use gen-idea for discovery and superman for the reviewed end-to-end flow.

Input

Accept spec text or one readable Markdown file, plus --output <path>; default <PROJECT_ROOT>/plan.md.

Run inside a Git repository. Reject a missing path-like input, an input/output collision, or an overwrite the user has not confirmed. Preserve the input verbatim in the plan.

Workflow

1. Read applicable repo instructions, the root README, and relevant code and tests.
2. Check that the design is settled enough to plan. Ask only blocking implementation questions. When discovery is still needed, stop and recommend gen-idea instead of guessing.
3. Define the final deliverables and numbered, verifiable requirements.
4. Set explicit scope bounds, allowed choices, milestones, dependencies, and whole-plan verification commands. Use relative dependencies, never dates or effort estimates.
5. Cite only repository paths you verified. Treat paths as feasibility hints, not mandates unless the input requires them.
6. Read assets/plan-template.md, write the plan once, and perform a final consistency check.

Quality Bar

• The plan must cover every approved outcome without inventing product scope.
• Requirements describe observable final state, not a fine-grained test matrix.
• Blocking decisions stay visible as DEC-N; write None when there are none.
• Write only the output plan and any parent directory the user approved.

Report the plan path and mark it unreviewed; superman adds independent review and a launch gate.