implement-and-verify

Test-driven development with acceptance criteria involves writing tests before implementation. This Skill automates that workflow by extracting acceptance criteria from user stories, generating tests first, then implementing code to pass those tests, ensuring 100% coverage of requirements before delivery.

Quality gates validate feature readiness by checking that ambiguities are resolved and acceptance criteria are sufficient before coding begins. This Skill enforces these gates to prevent premature implementation, reducing rework and ensuring clarity across the team.

Yes. Progressive delivery implements user stories in priority order, verifying each independently. This Skill enables shipping MVPs or incremental enhancements by completing and validating stories separately, accelerating time-to-value without waiting for full feature completion.

Verification compares implemented code against acceptance criteria through automated testing and linting. This Skill generates comprehensive verification reports confirming all acceptance criteria pass, providing confidence that requirements are fully satisfied before moving to the next story.

Specification-driven development organizes work into implementation plans with quality gates, test-first verification, and story-by-story delivery. This Skill executes that complete workflow—validating readiness, writing tests from specs, implementing incrementally, and generating verification artifacts for each story.

No. This Skill generates tests directly from acceptance criteria, eliminating manual test writing while ensuring comprehensive coverage. You focus on implementation; the Skill handles test generation, linting, and verification artifact production automatically.