phase-planner
Plans and divides tasks into actionable phases for system execution.
Install
mkdir -p .claude/skills/phase-planner && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18623" && unzip -o skill.zip -d .claude/skills/phase-planner && rm skill.zipInstalls to .claude/skills/phase-planner
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
승인된 task를 executable phase 집합으로 쪼개고 `phases.json`을 canonical 계획으로 고정한다.Key capabilities
- →Split approved tasks into smaller phases
- →Write JSON for each phase with allowed write paths and commands
- →Fill in acceptance commands and test policies for phases
- →Define required reads and starting points for phases
- →Generate `phases.json` as the canonical plan
How it works
The skill breaks down an approved task into smaller executable phases, then generates a `phases.json` file with detailed JSON for each phase.
Inputs & outputs
When to use phase-planner
- →Plan task phases
- →Create phases.json plan
- →Break down approved tasks
About this skill
Phase Planner
언제 사용하나
task.json이approved상태고task.json.intake가 현재spec.md와 동기화되어 있다.
먼저 확인할 것
AGENTS.mddocs/artifact-model.mddocs/runtime.mdworkflows/tasks/<task-id>/spec.mdworkflows/tasks/<task-id>/task.json
작업 방식
- task를 작은 phase들로 쪼갠다.
- 각 phase에
allowed_write_paths,acceptance.commands,test_policy,required_reads,starting_points,deliverables,completion_signal을 채운 JSON을 작성한다. - 추가 요구사항으로 spec을 바꿨다면
approve를 다시 실행해 intake를 재잠근 뒤python3 scripts/workflow.py plan <task-id> --from <phase-json>또는--stdin을 실행한다. phases.json은 오직plan명령만 canonical write owner다.
결과
workflows/tasks/<task-id>/phases.jsontask.json.active_phase_id- 다음 세션 kickoff가 읽을 bootstrap metadata
- 다음 stage:
phase-executor
When not to use it
- →When `task.json` is not in an `approved` state
- →When `task.json.intake` is not synchronized with `spec.md`
Limitations
- →Requires `task.json` to be in an `approved` state
- →Requires `task.json.intake` to be synchronized with `spec.md`
- →`phases.json` is only owned by the `plan` command
How it compares
This skill formalizes task breakdown into executable phases with structured JSON, providing a canonical plan for `phase-executor`, unlike ad-hoc task planning.
Compared to similar skills
phase-planner side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| phase-planner (this skill) | 0 | 3mo | No flags | Intermediate |
| trello | 41 | 2mo | Review | Beginner |
| executing-plans | 6 | 2mo | No flags | Intermediate |
| github-project-management | 4 | 5mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
executing-plans
obra
Use when you have a written implementation plan to execute in a separate session with review checkpoints
github-project-management
ruvnet
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
project-clickup
incidentfox
ClickUp project management integration for incident tracking and task management
coo-advisor
alirezarezvani
Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.
tlc-spec-driven
tech-leads-club
Project and feature planning with 4 phases - Specify, Design, Tasks, Implement+Validate. Creates atomic tasks with verification criteria and maintains persistent memory across sessions. Stack-agnostic. Use when: (1) Starting new projects (initialize vision, goals, roadmap), (2) Working with existing codebases (map stack, architecture, conventions), (3) Planning features (requirements, design, task breakdown), (4) Implementing with verification, (5) Tracking decisions/blockers across sessions, (6) Pausing/resuming work. Triggers on "initialize project", "map codebase", "specify feature", "design", "tasks", "implement", "pause work", "resume work".