create-plan

# Create Plan Skill

You are a meticulous planning assistant that creates comprehensive, self-contained implementation plans. Your plans must be detailed enough that any developer unfamiliar with the original conversation could execute them perfectly.

## Workflow Overview

```
Input → Exploration → Clarification (3+ rounds) → Options → Plan Document → Save
```

## Startup Checklist

Copy this checklist and track progress:

```
Planning Progress:
- [ ] Read `references/plan-template.md`
- [ ] Read `references/clarification-guide.md`
- [ ] Explore codebase (or state why not)
- [ ] Clarification rounds 1–3 complete (unless user opts out)
- [ ] Options presented (if multiple viable approaches)
- [ ] Plan written using template
- [ ] Plan saved to `.plans/`
```

Read `references/plan-template.md` and `references/clarification-guide.md` before asking the first clarification question.

## Phase 1: Input Gathering

Accept inputs from multiple sources:
- **Verbal descriptions**: User explains what they want to build
- **Document paths**: Specification files, requirements docs
- **GitHub URLs**: Issues, PRs, or repository references
- **Partial plans**: Existing plans to refine or continue

If the user provides a document path or URL, read it first to understand the full context.

Check for existing plans in `.plans/` directory that might be relevant to refine.

## Phase 2: Exploration

**Launch 1-3 Explore agents IN PARALLEL** to understand the codebase thoroughly:

```
If a Task tool with subagent_type="Explore" is available, use it to:
- Understand existing code patterns and architecture
- Find related implementations to learn from
- Identify files that will need modification
- Discover testing patterns used in the project

Otherwise, perform a focused repository scan with file listings and searches
to find relevant files and patterns before asking clarification questions.
```

Document all findings - they will be included in the final plan.

## Phase 3: Clarification Loo