GSD Planner

Transform goals into executable phase plans with dependency graphs and execution waves.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/apsulli/gmail-intel --skill gsd-planner-apsulli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GSD Planner
Source: https://github.com/apsulli/gmail-intel/tree/main/.opencode/skills/planner
Command: npx skills add https://github.com/apsulli/gmail-intel --skill gsd-planner-apsulli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague goals into structured, executable phase plans by breaking work into 2-3 task waves and mapping dependencies.

Core Features & Use Cases

  • Decompose phases into parallel-optimized plans with 2-3 tasks each
  • Build dependency graphs and assign execution waves
  • Derive must-haves using goal-backward methodology
  • Handle both standard planning and gap-closure mode
  • Return structured results to orchestrator
  • Use case: solo developers or small teams planning complex features with clear milestones

Quick Start

Provide the objective and constraints, and ask the planner to generate a 2-3 task plan with dependencies and execution waves

Frequently Asked Questions about GSD Planner

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

FAQPage Schema
How do I create an executable phase plan with task dependencies for a small team?

Executable phase planning transforms vague goals into 2-3 task waves with mapped dependencies. It decomposes phases into parallel-optimized execution waves, assigning tasks using goal-backward methodology to ensure milestones are met.

What is goal-backward verification in task planning?

Goal-backward verification in task planning derives must-have requirements by working backward from the final objective. It ensures every execution wave and dependency directly contributes to satisfying the overarching goal rather than introducing unnecessary work.

Can I use wave-based execution ordering for solo development planning?

Wave-based execution ordering supports solo developers planning complex features. It breaks work into structured task waves of 2-3 tasks each, allowing independent developers to sequence dependencies and execute parallel-optimized milestones.

How do I generate a dependency graph for phase planning?

Dependency graphs for phase planning are generated by decomposing objectives into discrete tasks and mapping their relationships. The planner assigns execution waves to each task, structuring the graph to support parallel execution where dependencies allow.

Does this phase planning approach handle gap-closure mode?

Gap-closure mode is supported alongside standard planning. It allows you to identify missing requirements between the current state and the goal, generating a 2-3 task wave plan with dependencies to close those specific gaps.

What is the best way to structure parallel-optimized plans with execution waves?

Parallel-optimized plans are structured by grouping independent tasks into 2-3 execution waves. The planner builds a dependency graph to identify which tasks can run concurrently, returning structured wave-based ordering results to the orchestrator.