Plan Implementation

Prompt file imported from Jeremy-Besson/KeepDebating (.claude/commands/plan.md). Fill in {{arguments}} before use. Copyright stays with the author.

Phase B: Planning

Context: {{arguments}}

1. Status Initialization

• Phase A: Analysis
• Phase B: Planning
• Phase C: Implementation, Testing & PR
• Final: Pull Request Created
• Current Status: Phase B - Planning Start

2. Instructions

1. Context Retrieval:

   • Look for the requirements file at Features/{{arguments}}/requirements.md.
   • Read the file and use it as the source of truth for this plan.
   • If not present, say so and stop.

2. Technical Blueprinting:

   • Produce a detailed technical blueprint for integration into the existing codebase.
   • Architecture: Define where the logic lives (which folders/files).
   • Signatures: Provide class, interface, or function signatures.
   • Data & Logic Flow: Explain how data moves through the new feature.

3. Risk Management:

   • Call out risks, assumptions, and the validation/testing strategy.

4. File Creation:

   • Save this plan as plan.md inside the Features/{{arguments}}/ directory.

3. Final Status

• Phase A: Analysis
• Phase B: Planning
• Phase C: Implementation, Testing & PR
• Final: Pull Request Created
• Current Status: Phase B - Planning Completed

4. Final Gate

• Use the AskUserQuestion tool with the question "Proceed to /implement?" and two options: label "Yes" and label "No".
• If Yes: invoke the /implement {{arguments}} skill.
• If No: await further instructions.