Planning Prompt

# {{FEATURE_NAME}} — Planning Session Prompt

> Paste everything below the horizontal rule into a new AI chat session.
> Run this to generate a phase plan from a feature description.
> The session will read the codebase, generate phase-N.md, and update status.md.
> Review the generated plan before running any execution sessions.

---

You are generating a **phase plan** for **{{FEATURE_NAME}}** in the repository at
`{{REPO_ROOT}}`.

## Step 1 — Read the project context

Read these files in full:

1. `{{DESIGN_FOLDER}}/context.md` — project conventions and layout
2. `{{DESIGN_FOLDER}}/spec.md` — feature specification (if it exists)
3. `{{DESIGN_FOLDER}}/status.md` — what phases/tasks already exist

## Step 2 — Understand the feature request

If `{{DESIGN_FOLDER}}/spec.md` exists and contains a filled-in feature
specification (not just template placeholders), use it as the feature
description. Confirm with the user: "I found spec.md — should I plan
based on this spec?" Proceed to Step 3 once the user confirms.

If `spec.md` does not exist or is still a template, ask the user to describe
what they want built. Ask clarifying questions if the request is ambiguous.
You need to understand:

- What is being built or changed
- Which files will be affected
- What the acceptance criteria should be

If the user has already provided a detailed description, proceed to Step 3.

## Step 3 — Analyze the relevant source files

Based on the feature description and context.md, identify all source files
that will need to be created or modified.

Read each of these files in full. For each file, note:
- Its current content and structure
- The exact locations where changes will be needed
- Any patterns or conventions that must be followed

## Step 4 — Determine the phase number

Read `{{DESIGN_FOLDER}}/status.md` and find the highest existing phase number.
The new phase will be N+1.

If no phases exist yet, start with phase-1.

## Step 5 — Generate the phase plan

Create `{{DESIGN_FOLDER}}/phase-N.md` following this exact structure for each task:

~~~markdown
# Phase N — <one-line description>

---

## Task N.1 — <short description>

**Target file:** `<repo-relative path>`

### What to change

<!-- For modifications to existing files, use Find/Replace: -->

Find: