specd

Route SpecD workflow changes to the next lifecycle skill based on state.

12|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/specd-sdd/SpecD --skill specd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specd
Source: https://github.com/specd-sdd/SpecD/tree/main/.gemini/skills/specd
Command: npx skills add https://github.com/specd-sdd/SpecD --skill specd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the current state of a change and tells you what to do next within a SpecD workflow.

Core Features & Use Cases

  • Routes between lifecycle steps without executing any phases.
  • Reads project status, context, and graph data to choose the next action.
  • Works across multiple lifecycle states (drafting, designing, ready, implementing, verifying, archivable).

Quick Start

Run the specd CLI with a status query to load state and see the recommended next skill.

Frequently Asked Questions about specd

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

FAQPage Schema
How do I determine the next step in a software change lifecycle workflow?

To determine the next step in a change lifecycle workflow, you can use a routing utility that reads project status and context to identify the current state and direct you to the appropriate next action.

What is the best way to route tasks across different lifecycle states like drafting and implementing?

Routing tasks across lifecycle states like drafting and implementing is best handled by a deterministic routing utility that analyzes graph data to choose the next action without executing the phases itself.

Can I execute lifecycle phases directly through a workflow routing CLI tool?

No, a workflow routing CLI tool does not execute lifecycle phases directly. It operates as a routing utility that provides deterministic instructions to guide you to the correct next skill.

How do I guide continuous change management across states from designing to archivable?

To guide change management from designing to archivable states, run a status query using the specd CLI to load current context and graph information, which outputs deterministic routing instructions for the next action.

Why does my change management workflow need a routing utility instead of direct execution?

A change management workflow needs a routing utility to separate state detection from execution, ensuring deterministic routing to the correct next skill based on project status without performing lifecycle changes itself.

Does the SpecD workflow router support multiple lifecycle states including verifying and ready?

Yes, the SpecD workflow router supports multiple lifecycle states including verifying and ready. It reads project status and graph data to provide deterministic routing instructions across these diverse states.