gsd:plan-phase

Generate phase-plan.md from wave descriptions and acceptance criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tDalile/dotfiles --skill gsd-plan-phase-tdalile
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd:plan-phase
Source: https://github.com/tDalile/dotfiles/tree/main/agents/skills/gsd/commands/plan-phase
Command: npx skills add https://github.com/tDalile/dotfiles --skill gsd-plan-phase-tdalile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts high-level phase or wave descriptions and acceptance criteria into a detailed, actionable execution plan, removing ambiguity and manual breakdown work for teams starting or refining a project phase.

Core Features & Use Cases

  • Structured Phase Planning: Breaks a phase into phases, waves, and atomic tasks and verifies plan structure.
  • Agent-driven Plan Generation: Spawns the gsd-planner agent to synthesize a comprehensive phase-plan.md and commits it to git.
  • Use Case: When beginning a frontend implementation wave, create a phase plan that lists waves, acceptance criteria-aligned tasks, and estimated sequencing for handoff to engineers.

Quick Start

Create a detailed phase plan from the current wave description and acceptance criteria, generate phase-plan.md with the gsd-planner agent, and commit it to git.

Frequently Asked Questions about gsd:plan-phase

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

FAQPage Schema
How do I break project phases into actionable tasks?▼

Project phase planning converts high-level wave descriptions and acceptance criteria into a detailed phase-plan.md by spawning a planner agent to structure work into waves and atomic tasks.

What is the best way to create execution plans from acceptance criteria?▼

Creating execution plans from acceptance criteria involves analyzing the requirements, optionally loading a codebase map for context, and generating a verified plan structure that aligns tasks with the criteria for engineering handoff.

Can I generate a task breakdown and commit it directly to git?▼

Yes, the task breakdown process generates a phase-plan.md file and commits it directly to git, ensuring the structured execution plan is version-controlled and ready for team collaboration.

Do I need a codebase map to create a phase plan?▼

A codebase map is optional for creating a phase plan. The planner agent can synthesize an execution plan from wave descriptions and acceptance criteria alone, but loading codebase context provides deeper implementation accuracy.

Why use an agent for task breakdown instead of manual planning?▼

Agent-driven task breakdown removes ambiguity and manual effort by automatically verifying the plan structure and aligning atomic tasks with acceptance criteria, ensuring a comprehensive execution plan for engineers.

Does this phase planning approach work for software and product development?▼

This phase planning approach works for both software and product development, applying to phase initialization, wave breakdown, and implementation planning where acceptance criteria are defined.