gsd-plan-phase

Generate executable PLAN.md phase prompts with research and verification steps.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-plan-phase-trucol270
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-plan-phase
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-plan-phase
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-plan-phase-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating roadmap phases and producing consistent executable PLAN.md prompts is time-consuming and error-prone, leading to misaligned expectations and delays.

Core Features & Use Cases

  • Executable phase prompts: Generate PLAN.md for roadmap phases that include a predefined research, planning, and verification workflow.
  • Integrated verification loop: Automatically run checks and capture results to inform next steps.
  • Reusable across roadmaps: Apply the same orchestration to multiple phases with minimal edits, ensuring standardization.
  • Example: A product team uses this to generate PLAN.md for a new feature phase with research notes, acceptance criteria, and verification steps.

Quick Start

Generate a PLAN.md for the specified roadmap phase that includes research, planning, and verification steps.

Frequently Asked Questions about gsd-plan-phase

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

FAQPage Schema
How do I automate roadmap phase planning and generate executable PLAN.md files?

Automating roadmap phase planning involves generating executable PLAN.md prompts that integrate research, planning, and verification workflows. This ensures each sequential project phase produces validated outputs through iterative refinement and automated orchestration.

What is an executable phase prompt and how does it integrate verification?

An executable phase prompt is a PLAN.md file defining research, planning, and verification steps for a roadmap phase. It integrates verification by automatically running checks and capturing results to inform next steps and iterative refinement.

Can I reuse the same planning and verification workflow across multiple sequential project roadmaps?

Yes, you can reuse the same orchestration across multiple roadmap phases with minimal edits. This standardizes the generation of PLAN.md files, ensuring consistent research, planning, and verification workflows across different projects.

How do I add research and acceptance criteria to a project phase plan?

To add research and acceptance criteria, generate a PLAN.md for the specified roadmap phase. The orchestration triggers optional research, spawns a planner, and runs verification to include notes and criteria automatically.

What is the best way to coordinate roadmap phases to avoid misaligned expectations and delays?

The best way to coordinate roadmap phases is automating executable PLAN.md prompt creation with integrated verification loops. This prevents time-consuming manual errors, ensuring validated outputs and aligned expectations across the team.