plan

name	plan
description	Break down a feature or project requirement into a structured development plan with tasks, milestones, and implementation order. Use when the user has a goal but needs to figure out what to build and in what sequence.

Plan

Turn a requirement or goal into a concrete, actionable development plan.

Steps

1. Understand the goal — Ask the user to describe what they want to build if not already provided. Clarify:

   • What problem does this solve?
   • Who are the users?
   • Any constraints (tech stack, timeline, existing codebase)?

2. Explore the existing codebase — If working inside an existing project, read key files to understand the current architecture before planning additions.

3. Draft the plan — Break the goal into phases:

   Phase 1 — Foundation (what must exist before anything else works)
   Phase 2 — Core features (the minimum viable version)
   Phase 3 — Polish & edge cases
   

   For each phase, list concrete tasks:

   • What file/module to create or modify
   • What the input/output or behavior should be
   • Any dependencies between tasks

4. Identify risks and unknowns — Flag anything uncertain: external APIs, unproven approaches, missing requirements.

5. Present the plan — Show the full plan clearly. Ask for feedback before starting implementation.

6. Start on demand — Only begin coding after the user confirms the plan. Start with Phase 1, task by task.

Output Format

## Goal
<one sentence>

## Phase 1 — <name>
- [ ] Task 1: <what + why>
- [ ] Task 2: <what + why>

## Phase 2 — <name>
- [ ] Task 3: ...

## Risks
- <risk or unknown>