plan-phase
/plan-phase
Plan the next unplanned phase in a task. Reads state.json to find the next not_started phase, then invokes Explorer to create a detailed implementation plan. Use when you need to create or revise a phase plan. Triggers on: '/plan-phase', 'plan the next phase', 'plan phase', 'create phase plan', 'plan unplanned phase'.
- Author
- mcouthon ↗
- Repository
- agents ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Plan the next unplanned phase in a task. Reads state.json to find the next not_started phase, then invokes Explorer to create a detailed implementation plan. Use when you need to create or revise a phase plan. Triggers on: '/plan-phase', 'plan the next phase', 'plan phase', 'create phase plan', 'plan unplanned phase'.
Triggers from the description
Original author description
Plan the next unplanned phase in a task. Reads state.json to find the next not_started phase, then invokes Explorer to create a detailed implementation plan. Use when you need to create or revise a phase plan. Triggers on: '/plan-phase', 'plan the next phase', 'plan phase', 'create phase plan', 'plan unplanned phase'.
How it works
- Live State
- What to do
- PAV Integration
SKILL.md preview
---
name: plan-phase
description: "Plan the next unplanned phase in a task. Reads state.json to find the next not_started phase, then invokes Explorer to create a detailed implementation plan. Use when you need to create or revise a phase plan. Triggers on: '/plan-phase', 'plan the next phase', 'plan phase', 'create phase plan', 'plan unplanned phase'."
arguments: [task_slug]
allowed-tools: [Read, Edit, "Task(Explorer)"]
---
# Plan the Next Unplanned Phase
## Live State
!`cat .tasks/${task_slug}/state.json 2>/dev/null | jq -r '.phases[] | select(.status == "not_started") | "Next unplanned: Phase \(.id) — \(.name)"' | head -1`
If no phase is shown above, all phases may already be planned or in
progress, or the task slug may be incorrect.
## What to do
1. Read the injected state above — it shows the next `not_started` phase
for task `$task_slug`. If empty, check whether the task exists and
whether all phases are already planned.
2. Read `.tasks/${task_slug}/task.md` for full task context — the phase
table, research findings, and the specific phase's details section.
3. Invoke Explorer to plan the phase:
- Use the Task tool to spawn an Explorer subagent
- Instruct Explorer: "Plan Phase [N] of task [task_slug]. Read
.tasks/[task_slug]/task.md for context. Create the phase plan at
.tasks/[task_slug]/plan/phase-N-[name].md."
- Explorer researches the phase, creates the plan, and updates
task.md to mark the phase as Planned
4. After Explorer completes, update state.json to signal planning is done:
- If you have `mcp__state-manager__*` tools (Conductor context): use
`state_update` to set the phase's `status` to "planned" and `owner`
to null
- Otherwise, use Edit on `.tasks/${task_slug}/state.json`: set the
phase's `status` field to "planned" and `owner` field to null
(planning complete, ready for build)
- PAV's scanner reads `status` and `owner` to display the phase's
state on its kanban board — "planned" with null owner signals
"ready for build"
5. If no `not_started` phase is found, report: "All phases are planned or
in progress. Use /build-phase N to start building, or /ship to commit
completed work."
## PAV Integration
- **Reads:** `state.json` phases where `status == "not_started"` — PAV's
scanner shows phase status on the kanban board (257 P3)
- **Writes:** `status: "planned"` and `owner` set to null after
planning — signals "ready for build" to PAV's scanner
- **Invocation:** PAV can invoke this command via socket steering (257 P5)
or Agent SDK (257 P6) to trigger planning from its UI
- **Output:** Explorer's plan file and task.md update are visible in
PAV's file browser and transcript view (257 P8)
Versions
The database has no other skills named plan-phase.
Database snapshot: 13.11.2026 · package version a1c29559a94f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100phase-review
Review implementation plans from the .tasks/ directory for flaws before committing — either a single phase (phase mode) or across all phases of a task for consistency (cross-phase analyze mode). Triggers on: 'use phase mode', 'review phase', 'review the plan', 'check phase',… - 100plan
Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding. - 100elaborate-phase
Elaborate a migration plan phase into a complete self-contained implementation plan. Use when user says "elaborate phase", "elaborate phase N", or "phase elaboration". Assesses codebase, writes detailed phase plan, then validates with dry walkthrough. - 100elaborate-phase
Elaborate a migration plan phase into a complete self-contained implementation plan. Use when user says "elaborate phase", "elaborate phase N", or "phase elaboration". Assesses codebase, writes detailed phase plan, then validates with dry walkthrough. - 100onboard
Drives the 9-phase install of Cowork AI OS. Reads state.md to know where the user is, runs the current phase, updates state.md, asks if they want to continue. Resumable from any phase. Trigger when the user says start onboarding, continue onboarding, where am I in onboarding, or types /onboard. - 100implementation
Pipeline phase skill for state `implementation`. Use when current_state is implementation.