Menu
Create a structured project plan from a task description. Use when: "plan", "design", "architect", "outline", "break down", "how should I build", "strategy", "roadmap"
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Full codebase audit: architecture health, dependencies, complexity, tech debt. Use when: "audit", "health check", "codebase analysis", "tech debt", "architecture review", "dependency check", "code quality"
Structured brainstorming with multiple approaches and tradeoffs. Use when: "brainstorm", "explore options", "what are my options", "compare approaches", "pros and cons", "which is better", "how should I", "alternatives"
Build error diagnosis and resolution. Use when: "build failed", "compile error", "bundler error", "fix build", "npm error", "type error", "won't compile"
Scaffold a new application with interactive dialogue. Use when: "create", "build me", "make an app", "new project", "scaffold", "generate app", "start new"
Generate a new custom skill from natural language description. Use when: "create skill", "new skill", "make a skill", "add command", "custom workflow", "skill template", "generate skill"
Systematic debugging with hypothesis-driven investigation. Use when: "debug", "not working", "bug", "broken", "error", "unexpected behavior", "fix issue", "investigate"
| 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 |
$ARGUMENTS
.agent/agents/project-planner.mdUse 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
| 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 |
Tell user:
Plan created: docs/PLAN-{slug}.md
Next steps:
- Review the plan
- Run `/create` to start implementation
- Or modify plan manually
| 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 |