spec-workflow

Specification-driven development enforces acceptance criteria (AC) verification by automatically validating AC adherence before allowing subtask progression. This mechanism ensures mandatory AC review and user confirmation at task start, preventing scope creep during implementation.

Specification-driven development is a process that reads specifications, parses acceptance criteria, and validates scope before implementation. It prevents scope creep by automatically enforcing AC checks, TDD cycles, and completion verification across Epic and Subtask phases.

You can automate TDD cycles and code reviews by applying a spec-driven workflow to Epic and Subtask progression. The system coordinates end-to-end across phases, automatically validating test planning, code reviews, and status updates before allowing upstream task handoffs.

To validate completion checks for specifications, apply a spec-workflow that verifies implementation phases against parsed acceptance criteria. The system reads specs from the specs/ directory and validates scope completion before allowing pull-request progression.

Yes, specification-driven workflow reads specifications directly from the specs/ directory to parse acceptance criteria. This folder structure is required to automatically validate scope and enforce TDD cycles during subtask implementation.

Automated specification enforcement is ideal when implementing new features across multiple phases where scope creep is a risk. Use it over manual reviews when you need mandatory AC adherence, automated TDD cycle validation, and structured handoffs between Epic and Subtask.