sdd-workflow

Spec-Driven Development workflow guidance for structured feature development. Use PROACTIVELY when the user discusses building features, planning implementations, capturing requirements, designing architectures, or shipping completed work. Guides through the 5-phase SDD workflow: Brainstorm → Define → Design → Build → Ship. This skill orients and routes; for any single phase's full methodology use its sdd-brainstorm / sdd-define / sdd-design / sdd-build / sdd-ship / sdd-iterate skill instead.

Ir a la instalación

Repositorio: luanmorenommaciel/agentspec
Última actividad en el origen: 4 de julio de 2026 a las 00:34
Idioma detectado de SKILL.md: inglés
Estrellas: 243
Forks: 126

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/luanmorenommaciel/agentspec --skill sdd-workflow

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

sdd-define

Phase 1 of the SDD workflow: capture and validate requirements in one pass. Owns the full Define methodology — classify the input (BRAINSTORM document, meeting notes, email thread, conversation, or direct request), extract entities (problem, users, MoSCoW goals, success criteria, acceptance tests, constraints, out of scope, assumptions), gather technical and data engineering context, calculate the clarity score against the 12/15 gate, fill gaps with targeted questions, and generate the DEFINE document from the shared template with correct status transitions. Use when the user wants to capture requirements, define the feature, structure project scope, or compute a clarity score — "capture requirements", "define the feature", "clarity score", "Phase 1", /define. Do not use for open-ended exploration of ideas and approaches (that is sdd-brainstorm, Phase 0) or for architecture and technical specification (that is sdd-design, Phase 2).

2026-07-15

sdd-design

Create the architecture and technical specification for a defined feature — Phase 2 of the SDD workflow. Transforms a validated DEFINE document into a DESIGN document: architecture diagram, components, inline architecture decision records, an agent-matched file manifest, KB-grounded code patterns, and a testing strategy — then updates the DEFINE status and hands off to /build. Use when requirements are captured and technical design is needed — "design the architecture", "technical design", "Phase 2", or /design pointed at a DEFINE_*.md file. Not for capturing or clarifying requirements (that is sdd-define, Phase 1) and not for implementing code (that is sdd-build, Phase 3).

2026-07-15

sdd-iterate

Update an existing SDD phase document (BRAINSTORM/DEFINE/DESIGN) mid-stream with full cascade awareness: classify the change (additive, modifying, removing, architectural), apply it with a version bump and change note, walk the cascade rules for downstream impact, and confirm with the user before applying any cascading edits. Owns the SDD change-management methodology: cascade rules, version-tracking and status-field obligations, and the iterate-vs-restart thresholds. Use when the user wants to update the requirements or design mid-stream — "requirements changed", "the design needs to change", "cascade the change" — or any existing phase document must change after downstream work has started. Do not use for a brand-new feature or a fundamentally different problem: a different problem, different users, or a change beyond roughly half the document calls for sdd-brainstorm/sdd-define instead of an iterate.

2026-07-15

Ver todos los de este repositorio

name

sdd-workflow

description

SDD Workflow Guide

You are the Spec-Driven Development workflow assistant. Help users navigate the 5-phase SDD workflow for structured, traceable feature development.

Phases

Phase	Command	Output	Purpose
0	`/agentspec:brainstorm`	`BRAINSTORM_{FEATURE}.md`	Explore ideas, compare approaches
1	`/agentspec:define`	`DEFINE_{FEATURE}.md`	Capture requirements (clarity >= 12/15)
2	`/agentspec:design`	`DESIGN_{FEATURE}.md`	Architecture + file manifest
3	`/agentspec:build`	Code + `BUILD_REPORT_{FEATURE}.md`	Implementation with tests
4	`/agentspec:ship`	`SHIPPED_{DATE}.md`	Archive + lessons learned

When to Guide

User says "I want to build..." → Suggest starting with /agentspec:brainstorm or /agentspec:define
User has requirements → Suggest /agentspec:define to structure them
User has a DEFINE doc → Suggest /agentspec:design to create architecture
User has a DESIGN doc → Suggest /agentspec:build to implement
User completed building → Suggest /agentspec:ship to archive

Workflow Rules

Phase 0 (Brainstorm) is optional — skip for well-defined tasks
Phase 1 (Define) requires clarity score >= 12/15 before advancing
Phase 2 (Design) must produce a complete file manifest with agent assignments
Phase 3 (Build) extracts tasks from the DESIGN manifest and delegates to specialist agents
Phase 4 (Ship) archives everything and captures lessons learned

Per-Phase Skills

Each phase's methodology lives in a dedicated skill; the phase agent and command are thin layers that load it. Read the phase skill when you need the HOW, not just the sequence:

Phase	Skill
0 Brainstorm	`sdd-brainstorm`
1 Define	`sdd-define`
2 Design	`sdd-design`
3 Build	`sdd-build`
4 Ship	`sdd-ship`
Cross-phase	`sdd-iterate`

The layering itself (agents execute, skills teach how, commands are entrypoints, KBs are source-of-truth) is defined in .claude/kb/shared/component-model.md.

Cross-Phase Updates

Use /agentspec:iterate to update any phase document when requirements change. It detects cascading impacts across phases.

Templates

Phase templates are available at .claude/sdd/templates/:

BRAINSTORM_TEMPLATE.md
DEFINE_TEMPLATE.md
DESIGN_TEMPLATE.md
BUILD_REPORT_TEMPLATE.md
SHIPPED_TEMPLATE.md

Workflow Contracts

Phase transition rules are defined in .claude/sdd/architecture/WORKFLOW_CONTRACTS.yaml.

Output Locations

All SDD documents are written to the user's project workspace:

Features: .claude/sdd/features/
Reports: .claude/sdd/reports/
Archive: .claude/sdd/archive/{FEATURE}/

sdd-workflow

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

SDD Workflow Guide

Phases

When to Guide

Workflow Rules

Per-Phase Skills

Cross-Phase Updates

Templates

Workflow Contracts

Output Locations

Más de este repositorio

SDD Workflow Guide

Phases

When to Guide

Workflow Rules

Per-Phase Skills

Cross-Phase Updates

Templates

Workflow Contracts

Output Locations