gsd-plan

Generate PLAN.md from ROADMAP.md and REQUIREMENTS.md with verification steps.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-plan
Source: https://github.com/alo-exp/silver-bullet/tree/main/skills/gsd-plan
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create PLAN.md with a clear phase goal, requirements mapping, task breakdown, and verification steps to guide and validate project planning stages.

Core Features & Use Cases

  • Read inputs from ROADMAP.md (phase goal) and REQUIREMENTS.md (REQ-IDs) and optional CONTEXT.md for locked decisions.
  • Write PLAN.md with sections: Goal, Requirements covered, Task breakdown, Per-task changes, Verification steps, Threat model, and Rollback.
  • Run Pre-Plan Quality Gates across 9 quality dimensions and surface findings before proceeding.
  • Present for Review by showing the completed PLAN.md and requesting confirmation or changes.

Quick Start

Create PLAN.md by outlining the phase goal, required inputs, tasks, and verification steps.

Frequently Asked Questions about gsd-plan

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

FAQPage Schema
How do I create a project plan with task breakdown and verification steps?

A project plan requires a structured PLAN.md file containing phase goals, task breakdowns, and verification steps. This skill reads ROADMAP.md and REQUIREMENTS.md inputs to generate that comprehensive planning document.

What should be included in a software project planning phase document?

A software project planning phase document needs a phase goal, requirements mapping, task breakdown, verification steps, threat model, and rollback section. This skill structures all these required sections into a standardized PLAN.md file.

How do I map requirements to specific implementation tasks in a development plan?

Requirements mapping is handled by reading REQ-IDs from REQUIREMENTS.md and generating a corresponding task breakdown in PLAN.md. This ensures every planned implementation task traces directly back to a documented requirement.

Can I use ROADMAP.md and CONTEXT.md as inputs for generating a development plan?

ROADMAP.md for phase goals and CONTEXT.md for locked decisions are fully supported as inputs. The skill reads these files alongside REQUIREMENTS.md to generate an accurate and contextually aware PLAN.md document.

How do I run quality checks before finalizing a software development plan?

Running quality checks before finalizing a plan is handled by 9 pre-plan quality gates that evaluate multiple dimensions. The skill surfaces all findings for user review before proceeding to generate the final PLAN.md output.

How do I add a threat model and rollback plan to my project roadmap?

Adding a threat model and rollback plan is achieved by generating a PLAN.md with dedicated sections for both. The skill ensures these safety and recovery protocols are structurally documented alongside the task breakdowns.