plan

name	plan
description	Create a structured project plan from a task description. Use when: "plan", "design", "architect", "outline", "break down", "how should I build", "strategy", "roadmap"
argument-hint	<task description>
user-invocable	true

/plan - Project Planning Mode

$ARGUMENTS

---

CRITICAL RULES

1. NO CODE WRITING - This command creates plan file only
2. Use project-planner agent - Read .agent/agents/project-planner.md
3. Socratic Gate - Ask clarifying questions before planning
4. Dynamic Naming - Plan file named based on task

---

Task

Use the project-planner agent with this context:

CONTEXT:
- User Request: $ARGUMENTS
- Mode: PLANNING ONLY (no code)
- Output: docs/PLAN-{task-slug}.md (dynamic naming)

NAMING RULES:
1. Extract 2-3 key words from request
2. Lowercase, hyphen-separated
3. Max 30 characters
4. Example: "e-commerce cart" → PLAN-ecommerce-cart.md

RULES:
1. Follow project-planner.md Phase -1 (Context Check)
2. Follow project-planner.md Phase 0 (Socratic Gate)
3. Create PLAN-{slug}.md with task breakdown
4. DO NOT write any code files
5. REPORT the exact file name created

---

Expected Output

Deliverable	Location
Project Plan	docs/PLAN-{task-slug}.md
Task Breakdown	Inside plan file
Agent Assignments	Inside plan file
Verification Checklist	Phase X in plan file

---

After Planning

Tell user:

Plan created: docs/PLAN-{slug}.md

Next steps:
- Review the plan
- Run `/create` to start implementation
- Or modify plan manually

---

Naming Examples

Request	Plan File
/plan e-commerce site with cart	docs/PLAN-ecommerce-cart.md
/plan mobile app for fitness	docs/PLAN-fitness-app.md
/plan add dark mode feature	docs/PLAN-dark-mode.md
/plan SaaS dashboard	docs/PLAN-saas-dashboard.md