spec-driven-dev-enforcer

To enforce specs-first coding, use a governance workflow that gates code generation by requiring a Requirements Document, Design Document, and Task Decomposition. This Skill halts implementation until explicit artifacts are created and approved, preventing ungoverned development.

Specs-first coding is a development process requiring explicit specifications before any implementation begins. It addresses the dark code issue by codifying a three-phase workflow—requirements, design, and task decomposition—ensuring artifacts are reviewed and approved before coding starts.

You create a requirements document and design doc by following a phase-driven workflow with structured prompts and templates. This Skill automatically guides artifact creation for each phase, halting progress until human review and explicit approval are provided before task decomposition begins.

Yes, you can use approval gates to halt code generation until design documents are reviewed. This Skill enforces explicit approvals at each phase of the development process, requiring human review of the requirements doc, design doc, and task decomposition before allowing any implementation to proceed.

Yes, this specs-first governance workflow works for task decomposition and feature work. It targets feature development across requirements, design, and task decomposition workflows, providing structured templates and guardrails to standardize artifact quality and traceability before coding begins.

The best way to standardize requirements documents and design docs is to use structured prompts and templates with enforced guardrails. This Skill provides standardized templates for each phase, ensuring artifact quality and traceability while codifying the three-phase workflow into your development process.