ClaudeCode-DevPlanBuilder

> Turn your product idea into a production-ready development plan in minutes

Tell Claude Code to read this repo, and it will guide you through building a comprehensive, paint-by-numbers development plan with all the testing, git discipline, and best practices baked in.

---

When a user asks you to help them create a development plan using this methodology, follow these exact steps:

Ask these questions ONE AT A TIME, waiting for responses:

1. "What's your project name?"
2. "What type of project is this? (CLI tool, web app, API, or library)"
3. "In one sentence, what does it do?"
4. "Who will use it? (e.g., developers, end users, admins)"
5. "What are the 3-5 must-have features for MVP?"
6. "Any technologies you must use or cannot use?"
7. "What's your timeline?"
8. "Any constraints I should know about?"

Write to PROJECT_BRIEF.md using this structure:

# Project Brief: {name}

## Overview

| Field | Value |
|-------|-------|
| **Project Name** | {name} |
| **Project Type** | {cli/web_app/api/library} |
| **Goal** | {one sentence} |
| **Timeline** | {timeline} |
| **Team Size** | 1 |

## Target Users

- {user type 1}
- {user type 2}

## Features

### Must-Have (MVP)

1. **{Feature Name}** - {description}
2. **{Feature Name}** - {description}
...

### Nice-to-Have (v2)

- {feature}
...

## Technical Requirements

### Tech Stack

| Component | Technology |
|-----------|------------|
| Language | {language} |
| Framework | {framework} |
| Testing | {test framework} |

### Constraints

- {constraint 1}
- {constraint 2}

## Success Criteria

1. {criterion 1}
2. {criterion 2}
...

## Out of Scope

- {thing 1}
- {thing 2}

Structure the plan with phases, tasks, and subtasks:

• Phases (0, 1, 2...): Major milestones
• Tasks (0.1, 1.2...): Features within a phase (one git branch