skills.rest
chenziyang110
chenziyang110COMMUNITY
Explore all skills by this author →
GitHub

spec-kit-workflow-routing

Route sp-* workflows with CLI validation via specify --help.

7|Updated Apr 7, 2026
Search Tags:#agent orchestration#spec-driven development#workflow routing#cli validation#consequence analysis#command discipline
One-click install
npx skills add https://github.com/chenziyang110/spec-kit-plus --skill spec-kit-workflow-routing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-kit-workflow-routing
Source: https://github.com/chenziyang110/spec-kit-plus/tree/main/templates/passive-skills/spec-kit-workflow-routing
Command: npx skills add https://github.com/chenziyang110/spec-kit-plus --skill spec-kit-workflow-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents accidental or premature entry into Spec Kit Plus workflow commands by helping you choose the correct sp-* route based on what the user explicitly asked for and the current invocation state.

Core Features & Use Cases

  • Workflow recommendation without auto-entry: Recommends an sp-* workflow only when it would materially improve the outcome, while avoiding silent activation during ordinary chat or coding.
  • Manual sp- interpretation support*: Detects when a user has already invoked an sp-* workflow and treats routing as complete, proceeding under that workflow’s contract.
  • CLI command discipline: Ensures any suggested or projected specify subcommand exists by validating against specify --help, avoiding invented or unsupported command names, including feature-creation guidance.
  • Consequence-aware routing: Chooses between sp-fast, sp-quick, sp-discussion, sp-specify, and sp-debug based on risk, lifecycle semantics, and failure/incident conditions.

Quick Start

Ask an AI agent to route your request inside a Spec Kit Plus repository by choosing the smallest safe sp-* workflow and the exact projected invocation placeholder (for example, tell it to decide whether to recommend {{invoke:specify}}, {{invoke:plan}}, or {{invoke:debug}}).

Frequently Asked Questions about spec-kit-workflow-routing

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

FAQPage Schema
How do I choose the correct Spec Kit Plus workflow for a specific coding task?▼

You choose the correct Spec Kit Plus workflow by evaluating risk, lifecycle semantics, and prerequisites to select the smallest safe sp-* route, preventing accidental or premature command activation.

What is the difference between sp-fast, sp-quick, and sp-specify workflows?▼

The difference between sp-fast, sp-quick, and sp-specify workflows lies in consequence-aware routing, which evaluates risk levels, failure conditions, and lifecycle semantics to select the correct command.

How do I validate specify CLI commands before routing a workflow?▼

You validate specify CLI commands by checking specify --help to enforce CLI surface validation, ensuring suggested subcommands exist and avoiding invented or unsupported command names during workflow routing.

Can I manually invoke an sp-* workflow without triggering automatic agent routing?▼

Yes, you can manually invoke an sp-* workflow; the system detects explicit invocations, treats routing as complete, and proceeds under that specific workflow's contract without auto-entry.

When should I avoid auto-activating spec-driven development workflows in chat?▼

You should avoid auto-activating spec-driven development workflows during ordinary chat to prevent silent activation, recommending an sp-* workflow only when it materially improves the outcome.

Why does my agent recommend sp-debug instead of sp-specify for my current request?▼

Your agent recommends sp-debug instead of sp-specify due to consequence-aware routing, which evaluates current failure conditions, incident states, and safety prerequisites to select the correct workflow.

Related Skills

Explore More Software Engineering Skills→
ZainEldeen-Ashraf-Ibrahim-Ibrahim-SamakZainEldeen-Ashraf-Ibrahim-Ibrahim-Samak

speckit-git-validate

Validate Git branch names against feature naming conventions and matching spec directories.

Community
Intermediate
jineynejineyne

speckit-plan

Generate implementation plans and design artifacts from spec-kit repositories.

Community
Advanced
guccangguccang
3

kanban-orchestrator

Decompose complex requests into tasks and route them to agent profiles.

Community
Advanced
chenziyang110chenziyang110
7

Test-Driven Development (Spec Kit Plus)

Enforce a failing test before production code changes in sp-* workflows.

Community
Basic