gsd-ns-workflow

Route user intent to the appropriate phase-pipeline skill for planning and execution.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-ns-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ns-workflow
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-ns-workflow
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-ns-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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?"

Frequently Asked Questions about gsd-ns-workflow

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

FAQPage Schema
How do I route intent to the right workflow phase in a multi-step development pipeline?

Intent routing analyzes user requests and maps them to the correct phase-pipeline skill for planning, execution, or verification. It eliminates planning friction by automatically directing gather, spec, plan, execute, and verify requests to the appropriate downstream skill.

What is the best way to manage phase progression from feature discussion to UAT verification?

Phase progression moves features step-by-step through discussion, specification, planning, execution, and UAT verification. Using an intent router advances you along the pipeline by mapping next or step-advance requests to consolidated progression behaviors.

How does intent routing work for consolidated phase commands like add, insert, and edit?

Intent routing for consolidated phase commands maps add, insert, remove, and edit requests to a unified phase skill. This ensures consistency by translating structural modification intents into the correct downstream skill invocation.

Can I use intent routing to map vague feature ideas into testable deliverables?

Yes, intent routing supports the full lifecycle flow from vague feature ideas to testable deliverables. It routes requests to gather context, generate a spec, create a plan, execute phases, and verify work through UAT.

Do I need specific downstream skills to execute the phases routed by this workflow orchestrator?

Yes, the workflow orchestrator requires downstream phase-pipeline skills to function. It emits exact sub-skill invocation names like gsd-spec-phase, gsd-plan-phase, and gsd-execute-phase, which must be available to process the routed intents.