Prompt file imported from chrisreddington/flight-school (.github/prompts/create-plan.prompt.md). Fill in {{specPath}} before use. Copyright stays with the author.

Create Implementation Plan

Name: create-plan
Author: chrisreddington

Specification: {{specPath}}

Context

Create an actionable implementation plan from an approved specification. SPEC = WHAT. PLAN = HOW.

Don't have a spec yet? Use /create-spec first.

Task

Consume spec handoff and produce executable plan:

1. Specification Intake

Parse goals, acceptance criteria, handoff section
Extract affected domains, file lists, specialist recommendations
Trust spec's analysis—don't re-research

2. Plan Development

Create numbered steps (1.1, 1.2, 2.1, etc.) with file references
Include verification command for every step
Link steps to spec stories (S1, S2, etc.)
Estimate complexity (S/M/L) per step

3. Specialist Consultation

Only invoke specialists in spec's "Affected Domains" checklist
Address blockers (max 3 iterations per specialist)
Incorporate guidance into step notes

4. Handoff Preparation

Complete Resumption Section for /implement-plan
Document rollback strategy per phase

Expected Output

Plan file at docs/plans/PLAN-{NNN}-{kebab-case-name}.md with:

Numbered steps with verification commands
File manifest (F1, F2, etc.) for traceability
Resumption Section ready for execution

{ "prompt": "# Create Implementation Plan\n\n**Specification**: `{{specPath}}`\n\n## Context\n\nCreate an actionable implementation plan from an approved specification. **SPEC = WHAT**. **PLAN = HOW**.\n\n**Don't have a spec yet?** Use `/create-spec` first.\n\n## Task\n\nConsume spec handoff and produce executable plan:\n\n### 1. Specification Intake\n- Parse goals, acceptance criteria, handoff section\n- Extract affected domains, file lists, specialist recommendations\n- Trust spec's analysis—don't re-research\n\n### 2. Plan Development\n- Create numbered steps (1.1, 1.2, 2.1, etc.) with file references\n- Include verification command for every step\n- Link steps to spec stories (S1, S2, etc.)\n- Estimate complexity (S/M/L) per step\n\n### 3. Specialist Consultation\n- Only invoke specialists in spec's \"Affected Domains\" checklist\n- Address blockers (max 3 iterations per specialist)\n- Incorporate guidance into step notes\n\n### 4. Handoff Preparation\n- Complete Resumption Section for `/implement-plan`\n- Document rollback strategy per phase\n\n## Expected Output\n\nPlan file at `docs/plans/PLAN-{NNN}-{kebab-case-name}.md` with:\n- Numbered steps with verification commands\n- File manifest (F1, F2, etc.) for traceability\n- Resumption Section ready for execution", "variables": [ "specPath" ], "notes": "Create implementation plan from specification (HOW to build) Arguments: Path to spec file (e.g., docs/specs/SPEC-001-feature.md).", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/chrisreddington/flight-school", "path": ".github/prompts/create-plan.prompt.md", "ref": "6d882f7117bb739b91d5c90b13732f0651437a6f", "url": "https://github.com/chrisreddington/flight-school/blob/6d882f7117bb739b91d5c90b13732f0651437a6f/.github/prompts/create-plan.prompt.md", "key": "chrisreddington/flight-school/.github/prompts/create-plan.prompt.md" } } }

create-plan

About

Create Implementation Plan

Context

Task

1. Specification Intake

2. Plan Development

3. Specialist Consultation

4. Handoff Preparation

Expected Output

Use it

Manifest

Reviews