vladm3105

doc-adr captures a single architectural decision using the Context-Decision-Consequences pattern, positioned as Layer 5 in the specification-driven development flow. It records…

Automates the full ADR lifecycle from source documents (BRD, PRD, EARS, BDD) or free-text prompts through generation, validation, and iterative refinement. Detects whether an ADR…

doc-adr-fixer consumes audit reports and patches ADRs to resolve structural, referential, and content issues identified during quality review. It supports both team-mode…

doc-bdd translates EARS requirements into Layer 4 acceptance scenarios using structured YAML (not Gherkin), each with Given-When-Then phases, element-level trace links to upstream…

doc-prd generates a Product Requirements Document as Layer 2 of the SDD workflow, converting business requirements into product capabilities, user personas, and measurable success…

doc-tdd generates Layer 7 TDD artifacts that translate component contracts into concrete test cases with quality thresholds. It maps BDD scenarios to unit, integration,…

doc-validator enforces consistency rules across your entire SDD documentation corpus—catching broken links, orphaned artifacts, cumulative-tag gaps, duplicate IDs, and…

gate-check automates the verification step in the change governance process by selecting the correct approval gate based on affected layers, running its entry criteria and error…

project-adopt brings an established codebase into the Specification-Driven Development workflow by detecting existing code and documentation, inferring the domain, and scaffolding…

Quality-advisor gives live feedback while you create or review SDD documents, catching completion gaps, documentation anti-patterns, tag compliance, and naming issues before…