phase-plan

Group issues into execution phases and promote ready items to Needs Spec.

6|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/withpiper/pipekit --skill phase-plan-withpiper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-plan
Source: https://github.com/withpiper/pipekit/tree/main/skills/phase-plan
Command: npx skills add https://github.com/withpiper/pipekit --skill phase-plan-withpiper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase planning groups a pool of issues into execution phases, enabling controlled batching and promotion to Needs Spec to start spec work.

Core Features & Use Cases

  • Read roadmap and phase state to determine phase priorities.
  • Assemble eligible issues into a phase (3-8 items) with dependency checks and milestone awareness.
  • Update PHASES.md and promote ready issues to Needs Spec, while surfacing status dashboards.

Quick Start

Plan the first phase by inspecting the current PHASES.md and ROADMAP.md, then run /phase-plan to propose and promote the initial phase.

Frequently Asked Questions about phase-plan

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

FAQPage Schema
How do I group Linear issues into execution phases for roadmap planning?

Execution phase planning groups eligible Linear issues into batches of 3-8 items, runs dependency checks, and promotes ready issues to Needs Spec. You can organize phases by inspecting ROADMAP.md and PHASES.md, then running a phase plan command to propose and promote the initial batch.

What is the best way to track milestones and dependencies across roadmap phases?

Tracking milestones and dependencies across roadmap phases involves reading roadmap state, applying dependency checks, and updating PHASES.md. The system coordinates milestones, cycles, and Linear state IDs to surface status dashboards and ensure phase sizing remains between 3 and 8 issues.

Can I use phase planning with pipelines governed by ROADMAP.md and Linear state IDs?

Yes, phase planning applies directly to pipelines governed by ROADMAP.md, PHASES.md, and Linear state IDs. It coordinates milestones, cycles, and dependencies within these files to determine phase priorities and promote ready items to Needs Spec for spec work.

How many issues should be in a single execution phase?

A single execution phase should contain between 3 and 8 issues. Phase sizing applies dependency checks and milestone awareness to assemble eligible items, ensuring controlled batching before promoting ready issues to Needs Spec.

How do I promote ready issues to Needs Spec for spec work?

Promoting ready issues to Needs Spec requires assembling eligible issues into a phase, verifying dependencies, and updating PHASES.md. Once dependency checks pass and milestone awareness is applied, the system promotes the batched items to start spec work.

Why does my phase plan require dependency checks before promoting issues?

Dependency checks are required before promoting issues to ensure controlled batching and execution readiness. The phase planning process applies these checks alongside milestone awareness to prevent promoting issues with unresolved dependencies to Needs Spec.