phased-planning
创建带有阶段提示的结构化实施计划,用于 Claude Code 执行。在构建复杂项目、创建实施路线图、将工作分解为阶段,或为多步骤开发生成 Claude Code 提示时使用。触发词包括"创建实施计划"、"将此项目分阶段"、"为此创建阶段"、"计划构建"、"分阶段实施"、"将其分解为阶段"。
name: phased-planning description: Creates structured implementation plans with phase prompts for Claude Code execution. Use when building complex projects, creating implementation roadmaps, breaking work into phases, or generating Claude Code prompts for multi-step development. Triggers include "create implementation plan", "phase this project", "create phases for", "plan the build", "phased implementation", "break this into phases".
Phased Planning Skill
Creates comprehensive phased implementation plans that generate copy-paste ready prompts for Claude Code execution, with success criteria and completion templates for each phase.
Triggers
- "create implementation plan"
- "phase this project"
- "create phases for"
- "plan the build"
- "phased implementation"
- "create Claude Code prompts"
- "break this into phases"
- "implementation roadmap"
Workflow
Phase 1: Project Analysis
Before creating phases, gather information:
1. Identify all components to build
2. Map dependencies between components
3. Determine optimal build order
4. Estimate phase complexity (3-12 tasks each)
Phase 2: Create Master Plan
Generate PLANNING/IMPLEMENTATION-MASTER-PLAN.md:
# [PROJECT NAME] - Implementation Master Plan
**Created:** [DATE]
**Project Path:** [PATH]
**Runtime:** [TECHNOLOGY]
---
## Pre-Implementation Checklist
### ✅ Documentation (Complete)
| Component | Location | Status |
|-----------|----------|--------|
| [Doc 1] | [path] | ✅ |
### ⏳ Code Implementation (To Build)
| Component | Location | Status |
|-----------|----------|--------|
| [Component 1] | [path] | ⏳ |
---
## Implementation Phases Overview
| Phase | Name | Files | Dependencies |
|-------|------|-------|--------------|
| 0 | Project Setup | package.json, tsconfig | None |
| 1 | Core Infrastructure | src/lib/* | Phase 0 |
| ... | ... | ... | ... |
Phase 3: Write Phase Prompts
For each phase, create PLANNING/implementation-phases/PHASE-X-PROMPT.md:
# Phase [X]: [NAME]
## Objective
[One sentence describing what this phase accomplishes]
---
## Prerequisites
- Phase [X-1] complete
- [Other requirements]
---
## Context Files to Read
[file1.md] [file2.md]
---
## Tasks
### 1. [Task Name]
[Description]
```[language]
// Complete code specification
2. [Task Name]
...
Success Criteria
- [Criterion 1]
- [Criterion 2]
Completion
Create PHASE-[X]-COMPLETE.md and commit:
git add -A
git commit -m "Phase [X]: [NAME] - [summary]"
### Phase 4: Create Quick-Start Prompt
Generate `CLAUDE-CODE-PHASE-0.md` at project root for easy copy-paste into Claude Code.
---
## Standard Phase Types
| Phase | Name | Purpose |
|-------|------|---------|
| 0 | Project Setup | package.json, tsconfig, dependencies, structure |
| 1 | Core Infrastructure | Config, logging, utilities, base clients |
| 2 | Framework | Base classes, types, patterns |
| 3 | Core Logic | Main business logic implementation |
| 4-N | Feature Phases | Individual features/components |
| Final | Integration | CLI, tests, end-to-end verification |
---
## File Organization
PROJECT/ ├── PLANNING/ │ ├── IMPLEMENTATION-MASTER-PLAN.md │ ├── PHASE-0-COMPLETE.md (created after phase 0) │ ├── PHASE-1-COMPLETE.md (created after phase 1) │ └── implementation-phases/ │ ├── PHASE-0-PROMPT.md │ └── PHASE-1-PROMPT.md ├── CLAUDE-CODE-PHASE-0.md (quick-start prompt) └── CLAUDE.md (updated with phase tracking)
**Note:** All `PHASE-X-COMPLETE.md` files go in `PLANNING/` directory, NOT in `implementation-phases/`.
---
## Phase Sizing Guidelines
| Complexity | Tasks | Approx. Time |
|------------|-------|--------------|
| Simple | 3-5 tasks | 10-20 min |
| Medium | 5-8 tasks | 20-40 min |
| Complex | 8-12 tasks | 40-60 min |
**Rule:** If >12 tasks, split into sub-phases.
---
## Completion Template
```markdown
# Phase [X]: [NAME] - COMPLETE
**Completed:** [DATE]
## Deliverables
- [x] [File/feature 1]
- [x] [File/feature 2]
## Verification
- `[command 1]`: ✅
- `[command 2]`: ✅
## Notes
[Any issues or deviations]
## Next Phase
Proceed to Phase [X+1]: [NAME]
Execution Protocol
CRITICAL: Autonomous Build Mode
ALWAYS run with --dangerously-skip-permissions for uninterrupted builds.
Before executing ANY phase task, verify autonomous mode:
# Check if running in dangerously-skip-permissions mode
# If user approval prompts appear, STOP and remind user to restart with:
claude --dangerously-skip-permissions
Starting a Phase
cd [project]
claude --dangerously-skip-permissions
# In Claude Code - AUTONOMOUS BUILD PROMPT:
"Read PLANNING/implementation-phases/PHASE-0-PROMPT.md and execute all tasks.
After completing each phase, automatically proceed to the next phase prompt
until all phases are complete. Create PLANNING/PHASE-X-COMPLETE.md after each
phase and git commit your changes. Do not wait for user approval between phases."
Auto-Progression Protocol
After completing a phase:
- ✅ Verify all success criteria
- ✅ Create
PLANNING/PHASE-X-COMPLETE.md - ✅ Git commit with phase message
- ✅ AUTOMATICALLY read and execute next phase - DO NOT wait for user
- ✅ Repeat until final phase complete
If NOT in --dangerously-skip-permissions mode:
- You will see approval prompts
- STOP and display this message to user:
⚠️ NOT IN AUTONOMOUS MODE Please restart Claude Code with: claude --dangerously-skip-permissions Then paste the build prompt again.
Completing a Phase
- Verify all success criteria checkboxes
- Create
PLANNING/PHASE-X-COMPLETE.mdfrom template - Git commit with phase message
- Immediately proceed to next phase (do not wait for user)
Best Practices
- Complete code in prompts - Don't leave implementation to inference
- Explicit success criteria - Checkboxes that can be verified
- Clear dependencies - State what must be complete first
- Git commits per phase - Clean history with phase messages
- No time estimates - Use phase order, not days/weeks
- Context files - Always specify what to read first
Integration
Works with:
- organized-codebase-applicator - For project structure
- phase-0-template - For quick project setup
- tech-stack-orchestrator - For component recommendations