gsd-plan-phase

Generate executable PLAN.md files for GSD project phases.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-plan-phase-pear-commerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-plan-phase
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-plan-phase
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-plan-phase-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GSD (Get Shit Done) project workflows often suffer from poorly defined phase plans that lead to misalignment, missed requirements, and rework, especially when teams need to quickly add new phases or address audit-identified gaps.

Core Features & Use Cases

  • Automated Phase Plan Generation: Creates structured, executable PLAN.md files for new roadmap phases, with optional domain research and PRD/acceptance criteria parsing.
  • Verification Loop Integration: Runs iterative verification checks to ensure plans meet project requirements before finalization, reducing rework.
  • Gap Closure Support: Reads existing VERIFICATION.md files to create targeted phases that address milestone audit findings. Use case: A software team using GSD workflows can use this skill to instantly generate a compliant phase plan for a new feature, skipping manual context gathering and verification steps.

Quick Start

Use the gsd-plan-phase skill to create a detailed executable plan for the next unplanned project phase.

Frequently Asked Questions about gsd-plan-phase

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

FAQPage Schema
How do I generate an executable phase plan from a PRD for a software project?

You can generate an executable phase plan by parsing PRD and acceptance criteria into a structured PLAN.md file. This process applies optional domain research and planner agent orchestration to ensure the phase plan aligns with project context and requirements.

How do I close milestone audit gaps identified in a VERIFICATION.md file?

To close milestone audit gaps, you read existing VERIFICATION.md files to create targeted phase plans that address the specific findings. This generates actionable PLAN.md outputs designed to resolve audit-identified deficiencies and satisfy milestone requirements.

What is phase plan verification and how does it prevent project rework?

Phase plan verification is an iterative checking process that ensures generated plans meet project requirements before finalization. By running verification loops against acceptance criteria, it eliminates misalignment and reduces the rework caused by poorly defined phase work.

Can I use automated plan generation for GSD workflows without manual context gathering?

Yes, you can use automated plan generation for GSD workflows to skip manual context gathering. The skill orchestrates planner agents and applies optional domain research to instantly produce compliant, executable phase plans for new roadmap features.

Does phase planning work with agent orchestration to validate project roadmaps?

Yes, phase planning works with agent orchestration by coordinating planner agents to construct and validate phase plans. The orchestrator drives iterative verification loops against project context to ensure the roadmap output is executable and compliant.

What are the limitations of automated phase plan generation for complex project roadmaps?

Automated phase plan generation relies on the accuracy of the parsed PRD and existing project context. While it runs verification loops to close gaps, highly ambiguous requirements may still require manual clarification before a fully executable PLAN.md can be finalized.