plan-phases

Plans substantial features through research, approval gates, and phased parallel execution.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/Takkuya/claude-skills --skill plan-phases-takkuya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-phases
Source: https://github.com/Takkuya/claude-skills/tree/main/plan-phases
Command: npx skills add https://github.com/Takkuya/claude-skills --skill plan-phases-takkuya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large features, refactors, and migrations often go wrong when coding starts before the idea is researched and scoped. This Skill enforces a disciplined workflow — read specs, research the codebase and web, pressure-test assumptions, then split work into approval-gated phases — so wrong directions are caught before thousands of lines are written. ## Core Features & Use Cases - Spec-anchored research: Reads product specs (SPEC.md, PRD.md, external docs), detects monorepo structure, and scopes research to only the relevant areas with parallel Explore agents. - Approval-gated planning: Produces a .plan/<slug>/ folder with specs.md, research.md, decisions.md, an HTML plan overview, and one detailed Markdown file per phase, each gated by explicit user approval. - Phased execution with validation: Fans out parallel agents per task within a phase, reconciles their output, runs tests, then has a blind three-agent validator panel (acceptance, correctness, regressions) review the result before the user sees it. - Use Case: You want to add a major feature to a monorepo. The Skill reads your PRD, scopes research to apps/mobile and services/api, challenges the approach, writes a reviewable HTML plan, then builds phase by phase — stopping for your approval at every gate. ## Quick Start Ask the assistant to plan a new feature or project before writing any code, for example by saying "help me plan this project" or invoking /plan-phases.

Frequently Asked Questions about plan-phases

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a large feature before writing code?

Invoke the plan-phases workflow with a request like "help me plan this project". It reads your product specs, researches the codebase and web in parallel, asks clarifying questions, then writes an HTML plan and per-phase Markdown files for your approval before any code is written.

How does phased execution with approval gates work?

Each phase is built by parallel task agents, reconciled, tested, and reviewed by a blind validator panel covering acceptance, correctness, and regressions. The phase is marked complete only after tests pass, and the workflow stops for your approval before starting the next phase.

Does plan-phases work in a monorepo?

Yes. It detects monorepo layouts such as apps/*, packages/*, and services/*, then asks which areas the feature touches. Research agents are dispatched only within the chosen scope, with cross-cutting dependencies flagged explicitly.

When should I not use a structured planning workflow?

Skip it for bug fixes, small tweaks, or single-file changes — the full research, HTML plan, and approval gates are deliberately heavyweight. It is designed for new projects, major features, refactors, and migrations where a wrong direction is costly.

What files does the planning workflow create?

It creates a .plan/<slug>/ folder containing specs.md, research.md, decisions.md, a plan.html overview, and a phases/ subfolder with one detailed Markdown file per phase plus per-phase validator review files. The folder is working scaffolding and can be gitignored.