gsd-ns-workflow

What problem does it solve?

It reduces planning-and-execution friction by routing a user’s request to the appropriate phase-focused phase-pipeline skill instead of forcing them to guess which command to use.

Core Features & Use Cases

• Intent-based phase routing: Sends “gather,” “spec,” “plan,” “execute,” “verify,” “edit,” “next,” “ultraplan,” and “plan review” requests to the correct downstream skill name.
• Covers full lifecycle flow: Supports moving from discussion through UAT/verification, plus iterating on phases and progressing step-by-step.
• Consolidated phase commands: Maps add/insert/remove/edit and next/do requests into the consolidated gsd-phase and gsd-progress behaviors for consistency.

Example use case: You want to turn a vague feature idea into a testable deliverable—start by gathering context, then request a spec, generate a plan, execute it in phases, and finally verify via UAT, with “next” advancing you along the pipeline.

Quick Start

Ask the AI to route your request to the correct phase-pipeline step, for example: "I have some context—what should we do next to plan and execute this phase workflow?"