sdd

Orchestrate spec-driven development from feature prompt through init, design, implement, and verify phases.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/nushey/sdd-flow --skill sdd-nushey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd
Source: https://github.com/nushey/sdd-flow/tree/main/skills/sdd
Command: npx skills add https://github.com/nushey/sdd-flow --skill sdd-nushey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-Driven Development orchestration helps teams turn a vague feature request into a disciplined, validated workflow without collapsing into a single monolithic prompt.

Core Features & Use Cases

  • Init → Design+Tasks → Implement → Verify flow: coordinates distinct subagent phases to keep context isolated and execution orderly.
  • PR-only verification: a verifier opens a pull request on PASS and never auto-merges, making reviews and human control central.
  • Convention-first execution: uses AGENTS.md as the source of truth and ensures it is kept current by the init phase.
  • Token-friendly orchestration: keeps the orchestrator thin while task-specific agents read only what they need.

Quick Start

Invoke the SDD orchestrator by writing: /sdd Add OAuth login with Google.

Frequently Asked Questions about sdd

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

FAQPage Schema
How do I run spec-driven development for a new feature from start to finish?

Spec-driven development orchestrates the full workflow by routing a feature prompt through sequential init, design, implement, and verify phases using isolated subagents. This keeps context thin and execution orderly without collapsing into a monolithic prompt.

What is the best way to automate task decomposition for repository-based engineering changes?

Automated task decomposition is handled by delegating feature prompts to designated subagents that generate design artifacts and sequential execution tasks. The orchestrator enforces a strict delegation contract to ensure agents read only what they need for each phase.

How does agent orchestration keep context isolated during complex code implementation?

Agent orchestration isolates context by keeping the main orchestrator thin and delegating all phase work to designated subagents. Task-specific agents read only the necessary repository conventions and intake artifacts for their specific execution phase.

How does spec-driven development handle pull request verification?

Pull request verification is handled by a designated verifier subagent that opens a pull request upon passing validation. It never auto-merges, ensuring human review and control remain central to the spec-driven development workflow.

Do I need an AGENTS.md file for spec-driven development workflow automation?

Yes, spec-driven development uses AGENTS.md as the source of truth for repository conventions. The init phase ensures this file is kept current before task decomposition and implementation subagents begin their work.

When should I not use a spec-driven development orchestrator?

You should avoid spec-driven development orchestration for changes that do not require sequential task execution or repository-based engineering changes. It is designed for disciplined, multi-phase validation rather than quick, isolated edits.