sdd-router

Diagnose repository state and recommend the next SDD pipeline step.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/juan-estrada-itti/way-of-work-tools --skill sdd-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-router
Source: https://github.com/juan-estrada-itti/way-of-work-tools/tree/main/skills/sdd-router
Command: npx skills add https://github.com/juan-estrada-itti/way-of-work-tools --skill sdd-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the current state of a repository and prescribes the next SDD pipeline step based on PIPELINE-TRANSITIONS.yml rules.

Core Features & Use Cases

  • Diagnostic routing: scans artifacts (discovery, PRD, RFC, etc.) and applies 14 routing rules plus 4 validations to determine the recommended next skill.
  • Guidance with rationale: outputs the next skill, why it was chosen, and any gate or human input required.
  • Flexible context handling: supports greenfield (new initiatives) and brownfield (existing codebases) contexts.

Quick Start

Ask SDD Router to diagnose your repo state and return the recommended next skill with rationale.

Frequently Asked Questions about sdd-router

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

FAQPage Schema
How do I determine the next pipeline step for my repository?

To determine the next pipeline step, this skill diagnoses your repository state by scanning existing artifacts like PRD or RFC files, then applies routing rules to prescribe the next action. It outputs the recommended step, rationale, and required gate.

What is SDD routing and how does artifact discovery work?

SDD routing is the process of diagnosing a repository's current state by discovering existing artifacts like PRDs and RFCs. It uses a three-question diagnostic flow and transition rules to identify what development step should happen next.

Can I use pipeline transition rules for an existing codebase?

Yes, pipeline transition rules support both greenfield initiatives and brownfield existing codebases. The diagnostic flow adapts to your specific context by scanning available artifacts to determine the correct next step regardless of project age.

How do I start repository discovery when I have zero artifacts?

When starting from zero artifacts, the skill uses a diagnostic three-question flow to establish your repository context. This flow identifies the baseline state and outputs the initial next skill, rationale, and required gate from the transition rules.

What's the best way to enforce pipeline gates and decision routing?

The best way to enforce pipeline gates is to use the PIPELINE-TRANSITIONS.yml file as the source of truth. The skill reads this file, applies 14 routing rules and 4 validations, and outputs any required human input or gate before proceeding.

Why does my pipeline routing skip required validation steps?

Pipeline routing skips validation when repository artifacts do not meet the gate conditions defined in PIPELINE-TRANSITIONS.yml. The skill applies 4 specific validations during diagnosis and requires human input if any gate fails before recommending the next skill.