ls plans/ 2>/dev/null | head -5

mkdir -p plans/{name}

# {Plan Name}

## Documentation Files (READ THESE FIRST)
- `plans/{name}/PLAN.md` - Project structure and implementation overview (if created)
- `plans/{name}/DESIGN.md` - Visual specification (if created)
- `plans/{name}/API.md` - API endpoints documentation (if created)
- `plans/{name}/prd.json` - Feature list with verification steps
- `plans/{name}/progress.txt` - Progress log from previous sessions

## Quick Start
1. Read ALL documentation files above before starting
2. Read prd.json to see all features
3. Read progress.txt for context from previous sessions
4. Pick ONE feature to work on (highest priority with passes: false, by category order)
5. Complete all verification steps for that feature
6. Update prd.json passes to true
7. Commit with descriptive message
8. Log learnings to progress.txt

## Tech Stack
{tech_stack_from_user_input}

## Project Requirements
{project_requirements_if_provided}

## Reference Project
{reference_project_if_provided}

## Rules
- **Never remove or modify features in prd.json** (only change passes field)
- Always verify ALL steps before marking passes: true
- **One feature per session** - do not attempt multiple features
- Always commit working code

## Prioritization
When choosing your next task, prioritize in this order:
1. **Tasks with a `priority` key** - lower number = higher priority (e.g. `priority: 1` before `priority: 2`)
2. **Architectural decisions and core abstractions** (highest)
3. **Integration points between modules**
4. **Standard features and implementation**
5. **Polish, cleanup, and quick wins** (lowest)

Categories provide context, not strict ordering. Always check for explicit priority keys first.

**Note:** When adding new items to prd.json, **omit the `priority` field** unless specifically asked to include it.

## Testing Requirements
{testing_requirements_from_user_input}

### Test Structure
| File Type | Test Type | Location | Enforcement |
|-----------|-----------|----------|-------------|
{test_structure_table}

### When Implementing a Feature
1. Write the implementation code
2. Write unit tests for applicable files
3. Write E2E tests for UI interactions (verification steps from prd.json)
4. Run all feedback loops to verify everything passes
5. Only commit when all tests pass

## Feedback Loops (Run Before Committing)
Before committing any changes, run ALL feedback loops:

{feedback_loop_commands}

Or run all tests at once: `{combined_test_command}`

Do NOT commit if ANY feedback loop fails. Fix issues first.

## Quality Expectations
- This codebase will outlive the current implementation
- Every shortcut becomes technical debt
- Small, focused changes - quality over speed
- One logical change per commit
- Fight entropy - leave the codebase better than you found it

## Completion Promises (IMPORTANT)

When running via ralph.sh, you MUST output one of these promises before finishing:

**After completing a feature and committing:**

**If ALL features in prd.json are complete:**

**If you encounter an unresolvable blocker:**

Always log blockers to progress.txt before outputting BLOCKED.

# {Plan Name}

## Parent Plan
This plan inherits shared settings from `plans/{parent_plan}/CLAUDE.md`.

For tech stack, testing requirements, feedback loops, and quality expectations, see the parent plan.

## Documentation Files
- `plans/{name}/PLAN.md` - Implementation overview for this feature (if created)
- `plans/{name}/DESIGN.md` - Visual specification for this feature (if created)
- `plans/{name}/API.md` - API endpoints for this feature (if created)
- `plans/{name}/prd.json` - Feature list with verification steps
- `plans/{name}/progress.txt` - Progress log for this feature

## Feature Description
{feature_description}

## Feature-Specific Requirements
{feature_requirements_if_provided}

## Quick Start
1. Read the parent plan's CLAUDE.md for project-wide settings
2. Read ALL documentation files in this plan folder
3. Read prd.json to see all tasks for this feature
4. Read progress.txt for context from previous sessions
5. Pick ONE task to work on (highest priority with passes: false)
6. Complete all verification steps for that task
7. Update prd.json passes to true
8. Commit with descriptive message
9. Log learnings to progress.txt

## Rules
- **Never remove or modify features in prd.json** (only change passes field)
- Always verify ALL steps before marking passes: true
- **One task per session** - do not attempt multiple tasks
- Always commit working code
- Follow the parent plan's testing and feedback loop requirements

## Completion Promises (IMPORTANT)

After completing a task and committing:

If ALL tasks in prd.json are complete:

If you encounter an unresolvable blocker:

[]

# Progress Log for {Plan Name}

## Plan Created - {current_date}
- Project: {project_description}
- Tech Stack: {tech_stack}
- Ready for first feature implementation

# Progress Log for {Plan Name}

## Plan Created - {current_date}
- Feature: {feature_description}
- Parent plan: plans/{parent_plan}
- Ready for first task implementation

# {Plan Name} - Implementation Plan

## Overview
{Brief description}

## Architecture
{Describe the high-level architecture}

## Project Structure

## Implementation Phases
1. Phase 1: {description}
2. Phase 2: {description}
3. Phase 3: {description}

# {Plan Name} - Design Specification

## Visual Specification
{Describe the visual layout}

## Color Palette
- **Background**: `#xxx`
- **Primary**: `#xxx`
- **Text**: `#xxx`

## Typography
- **Font family**: {font}
- **Headings**: {size}
- **Body**: {size}

## Layouts
{Describe layouts with ASCII diagrams}

# API Specification

All endpoints are relative to the base API URL.

## GET /api/endpoint

### Request
{Parameters}

### Response
```json
{
  "field": "value"
}

{
  "field": "value"
}

{
  "success": true
}

## Step 6: Offer to Commit

After creating all files, ask the user:
"Plan folder created at `plans/{name}/`. Would you like me to commit this?"

If yes, commit with message: "Add {plan_name} plan folder with initial structure"

## Reference

See `.claude/templates/plan-CLAUDE.md` for the template structure.