Blueprint Generate

Blueprint — Generate plan

Generate an implementation plan from the Q&A session.

Step 1: Resolve template

Recall the template name from the blueprint Q&A conversation. Read references/templates.json and find the matching template.

Step 2: Generate slug

Create a concise 2-5 word kebab-case slug (max 50 chars) for the feature. Sanitize: lowercase, alphanumeric + hyphens only, no leading/trailing hyphens. If blueprint/<slug> already exists, append -2, -3, etc.

Step 3: Create plan directory

mkdir -p blueprint/<slug>

Step 4: Refine the prompt

Use the most recent refined prompt from the Q&A conversation. If for any reason it wasn't shown during Q&A, generate it now — see references/refine-prompt.md.

Step 5: Write the plan

See references/write-plan.md.

Append this progress line at the end of every message during the Write phase:

✓ Explore  ✓ Plan  ● Write  ○ Refine

Place the line after all other content, separated by a blank line.

Step 6: Refinement

See references/refinement.md.

Plan questions

Output a numbered question list in the conversation (NOT in the plan file):

> Answer with shorthand like `1a, 2b, 3e` or write freely.

---

**Q1. [Question text]**

_Context: [1-2 line snippet from the plan]_

a) Option A
b) Option B
c) Option C
d) Other (describe)


**Q2. [Question text]** (select all that apply)

_Context: [1-2 line snippet from the plan]_

a) Option A
b) Option B
c) Other (describe)


**Q3. [Open-ended question text]**

_Context: [1-2 line snippet from the plan]_

Leave two blank lines between questions. Leave a blank line between the question text, context line, and options. For questions with clear enumerable options, provide lettered choices. Always include a final "Other (describe)" option so the user can provide their own answer. If a question is better answered with free text, omit choices. Focus on decisions that meaningfully affect the implementation — not trivial or obvious choices.

Refine prompt

Synthesize the Q&A conversation into a refined version of the original prompt. Rules:

• NEVER change the wording of the original prompt — keep it exactly as written
• ONLY add new bullet points (using * syntax) to incorporate the clarifications
• Insert new bullet points in logical locations near related content
• Each bullet should synthesize a question and its answer into one concise statement
• Add exactly one bullet per question-answer pair
• Do not add explanations or commentary

Plan refinement

Inform the user:

• The plan is ready — show the path in a code block so it's easy to copy
• They can chat to refine the plan freely
• Ask "what are the open questions?" to get a list of any open questions to resolve
• Do NOT modify any files other than the plan until the user explicitly confirms they are ready to move to implementation

Then continue for as many rounds as the user wants. Each round, the user may:

• Ask for free-form changes to the plan
• Ask for open questions to resolve

When the user asks for changes:

• Only modify the plan file — do not create or modify any other files
• Preserve the plan's overall structure
• Make targeted edits that address user feedback
• After significant edits, offer to regenerate the question list

When generating open questions, follow the format in plan-questions.md.

Progress indicator

Append this progress line at the end of every message during refinement:

✓ Explore  ✓ Plan  ✓ Write  ● Refine

Place the line after all other content, separated by a blank line.

Write plan

Write the plan to blueprint/<slug>/plan-<slug>.md.

Use the refined prompt as your primary input — it contains both the original feature description and all clarifications from the Q&A. Before writing:

• Explore the existing codebase as needed
• Understand current patterns, architecture, conventions

Follow the template's prompt field for the plan structure and sections. The prompt is a list of strings — join them with newlines to get the full instructions.

CRITICAL:

• Never write implementation code during this time