sdd-metodologia

Alias -> sdd-06-analyze. Use /sdd:06-analyze instead.

SDD Phase 0 — Define project governance principles and coding standards

SDD Phase 1 — User Specs — user stories, functional requirements (FR), success criteria (SC) from natural language

SDD Phase 2 — Technical Specs — architecture, data model, API contracts, technology decisions

SDD Phase 3 — BDD Analysis — requirements quality checklists (not implementation testing) [GATE G1]

Pipeline conductor for Spec Driven Development. Reads project state, determines the optimal next action, enforces gates, and delegates to the correct skill. The user should never need to remember which command comes next.

SDD Phase 0 — Define governance principles, coding standards, quality gates, and TDD policy. Enhanced: validates context.json, updates pipeline state, suggests workspace creation.

SDD Phase 1 — User Specs from natural language. FR-NNN, SC-NNN, acceptance scenarios. Enhanced: bug-fix intent detection, semantic diff on re-run, workspace RAG capture.

SDD Phase 2 — Technical Specs: architecture, data model, API contracts, technology decisions. Enhanced: Tessl tile discovery, context validation, schema enforcement.

SDD Phase 3 — BDD Analysis quality checklists. [GATE G1] Enhanced: mandatory gate enforcement, FR→plan alignment check.

SDD Phase 4 — Gherkin BDD test specs with cryptographic assertion hashing. Enhanced: SHA-256 hash generation, traceability tag validation, assertion integrity.

4 hooks across 4 events