gsd-phase-planner

Initialize roadmap phases and generate PLAN.md and CONTEXT.md artifacts.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/da-moon/manus-skills --skill gsd-phase-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-phase-planner
Source: https://github.com/da-moon/manus-skills/tree/main/skills/gsd-phase-planner
Command: npx skills add https://github.com/da-moon/manus-skills --skill gsd-phase-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Teams planning complex roadmaps often struggle to coordinate research, context gathering, plan creation, verification, and phase CRUD operations across multiple phases. This Skill provides a structured workflow to systematically create phase artifacts that align with the roadmap and enable consistent execution.

Core Features & Use Cases

  • Workflow-driven phase planning: initialize phase data from ROADMAP.md, gather context, and create PLAN.md artifacts.
  • Phase CRUD and verification: add/insert/remove/reorder phases, verify plans against goals, and commit state updates.
  • Artifacts orchestration: generate CONTEXT.md, RESEARCH.md, PLAN.md, and STATE-driven summaries to keep stakeholders aligned.

Quick Start

Plan the next phase by invoking the Planner workflow to initialize the phase context, generate a PLAN.md, and prepare artifacts for verification.

Frequently Asked Questions about gsd-phase-planner

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

FAQPage Schema
How do I plan and manage roadmap phases across multiple milestones?

You can plan and manage roadmap phases by initializing phase data from ROADMAP.md, gathering context, and generating PLAN.md and CONTEXT.md artifacts to enable consistent phase-level execution and documentation. The workflow also verifies plans and commits state updates.

What is the best way to organize product roadmap documentation for phase execution?

Organize roadmap documentation by orchestrating artifacts like CONTEXT.md, RESEARCH.md, PLAN.md, and STATE-driven summaries. This keeps stakeholders aligned and provides a structured workflow to systematically create phase artifacts that align with the roadmap.

Can I add, remove, or reorder phases in an existing roadmap workflow?

Yes, you can perform phase CRUD operations to add, insert, remove, or reorder phases. The workflow enforces verifying plans against goals and committing state updates using included scripts to maintain roadmap consistency.

Do I need a ROADMAP.md file to start the phase planning workflow?

Yes, a ROADMAP.md file is required. The workflow enforces initializing phase context directly from ROADMAP.md before gathering research and generating the PLAN.md and CONTEXT.md artifacts needed for verification and execution.

How does phase verification work during product roadmapping?

Phase verification works by checking generated plans against roadmap goals before committing state updates. This ensures phase-level planning aligns with overall milestones and that documentation artifacts like PLAN.md remain consistent with the intended roadmap execution.

What limitations exist when using scripts for roadmap phase planning?

The workflow is limited to processing phase data defined within ROADMAP.md and relies on generating specific markdown artifacts. It enforces a strict initialize-gather-verify-commit sequence, meaning deviations from this structured planning workflow are not supported.