gsd-ns-workflow

Route user intent to the appropriate Get Shit Done phase-pipeline skill.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-ns-workflow-beibei-clic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ns-workflow
Source: https://github.com/BeiBei-Clic/ai-skills/tree/main/gsd-ns-workflow
Command: npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-ns-workflow-beibei-clic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of deciding which GSD phase command to run, so users can move from discussion to planning, execution, verification, and progress without memorizing command names.

Core Features & Use Cases

  • Intent-based phase routing: Maps what the user wants (context gathering, spec clarification, plan creation, execution, UAT verification) to the correct sub-skill target.
  • Centralized consolidated workflow: Uses consolidated routing so former add/insert/remove/edit-phase and next/do commands are absorbed into the appropriate modern targets.
  • Direct Skill tool invocation: Delegates execution to the matched phase-pipeline skill via the Skill tool.

Use Case: When you describe what you are trying to do in a project (e.g., you have notes and want to build a plan, then later want to execute and verify), gsd-ns-workflow routes each request to the correct downstream phase skill.

Quick Start

Ask the AI to plan or execute a phase by describing your goal, for example: "Create a PLAN.md for the next phase and then propose how we should verify it."

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 project requests to the right planning or execution phase?

Intent-based phase routing maps user goals, such as creating a PLAN.md or performing UAT verification, to the correct downstream pipeline skill. It eliminates the need to memorize command names by directly delegating execution to the matched target.

What is the best way to manage workflow transitions from planning to UAT verification?

Centralized consolidated routing manages workflow transitions by absorbing former phase management commands into modern targets. It handles the progression from discussing inputs and specifying deliverables to execution and final UAT verification.

Can I use intent mapping to create a PLAN.md file without knowing specific commands?

Yes, intent mapping allows you to create a PLAN.md file by describing your goal in natural language. The workflow identifies your intent and invokes the matched sub-skill directly without requiring specific command names.

Does this workflow routing support phase management for both execution and progress tracking?

Yes, workflow routing supports phase management for both execution and progress tracking. It maps user intent for executing phase plans and managing progress directly to the appropriate downstream skill pipeline.

When should I not use centralized consolidated routing for project pipelines?

Avoid centralized consolidated routing if your project requires manual command selection or operates outside the standard planning, execution, and verification pipeline. It is designed specifically for intent-based phase progression and direct skill invocation.