GSD Planner

Convert goals into phase plans with dependency graphs and task waves.

Updated Aug 7, 2025
One-click install
npx skills add https://github.com/hGriff0n/velopitt --skill gsd-planner-hgriff0n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GSD Planner
Source: https://github.com/hGriff0n/velopitt/tree/main/.agent/skills/planner
Command: npx skills add https://github.com/hGriff0n/velopitt --skill gsd-planner-hgriff0n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to turning high-level goals into executable planning artifacts, enabling consistent planning outputs and repeatable processes.

Core Features & Use Cases

  • Plan decomposition: Break goals into 2-3 task waves with clear dependencies.
  • Dependency graphs: Build wave-based execution order and identify prerequisite work.
  • Goal-backward verification: Derive must-haves and success criteria to ensure delivery.

Quick Start

To start planning, provide a high-level objective and I will generate a phase-plan skeleton with waves and tasks.

Frequently Asked Questions about GSD Planner

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

FAQPage Schema
How do I break down a high-level goal into executable phase plans?

To break down goals, you provide a clear objective and constraints to generate a phase plan skeleton. This produces structured waves of 2-3 tasks with dependency graphs and goal-backward verification.

What is goal-backward verification in task planning?

Goal-backward verification derives must-haves and success criteria from your final objective. It ensures every wave and task within the phase plan directly contributes to the targeted delivery.

Can I use phase planning to manage task dependencies for a small team?

Yes, phase planning applies to solo AI workflows or small teams to manage task dependencies. It produces a reproducible format with wave-based execution order to identify prerequisite work.

What do I need to provide to generate a phase plan with task breakdown?

You need to provide clear objectives and constraints to generate a phase plan. This input allows the system to produce must-haves, artifacts, and structured wave sequencing.

When should I avoid using a dependency graph for task management?

You should avoid dependency graph task management if your objective lacks clear constraints or cannot be broken into 2-3 task waves. The planning process requires defined goals to build reproducible wave sequencing.