What is the Spec-TDD workflow?

Spec-TDD stands for Specification-Test-Driven Development. It is a process where you write a detailed specification first, then write tests based on that spec, and only then write the implementation code to pass those tests.

When should I choose an acceptance test over a unit test?

According to the STDD workflow, if a test requires mocking repositories, external services, or complex dependencies, it should be an acceptance test. Unit tests are reserved for isolated logic.

How does this skill handle requirement tracking?

The skill uses specific markers (like [U][X]) within the specification file to track whether a requirement has a corresponding test and whether the implementation code has been completed.

Why does the skill require running pre-commit hooks?

Pre-commit hooks are enforced to ensure that code is not only functionally correct but also adheres to project linting, formatting, and static analysis standards before completion.

Spec-Test-Driven Development

Name: Spec-Test-Driven Development
Author: craigtkhill

bycraigtkhill

セキュリティとテスト

Enforces a rigorous specification-first workflow that ensures every feature is documented, tested, and verified before final implementation.

概要

The Spec-Test-Driven Development (STDD) skill provides a disciplined framework for building software features by prioritizing documentation and verification. It guides Claude through a strict five-step cycle: drafting formal specifications with user stories and requirements, writing unit or acceptance tests before implementation, developing minimal code to pass those tests, and finally verifying the output through automated test suites and pre-commit hooks. This skill is essential for developers who require high-quality, bug-resistant code and want to maintain clear traceability between business requirements and technical implementation.

主な機能

Smart differentiation between unit tests and integration-heavy acceptance tests
Specification-first requirement drafting using Gherkin-style scenarios
Enforced verification through automated test runners and pre-commit hooks
Automated tracking of requirement completion via inline status markers
0 GitHub stars
Mandatory test-before-code workflow to ensure comprehensive coverage

ユースケース

Standardizing development workflows across a team to improve code auditability
Building mission-critical features where functional accuracy is non-negotiable
Scaling complex codebases while maintaining a robust regression test suite

概要

主な機能

Smart differentiation between unit tests and integration-heavy acceptance tests
Specification-first requirement drafting using Gherkin-style scenarios
Enforced verification through automated test runners and pre-commit hooks
Automated tracking of requirement completion via inline status markers
0 GitHub stars
Mandatory test-before-code workflow to ensure comprehensive coverage

ユースケース

Standardizing development workflows across a team to improve code auditability
Building mission-critical features where functional accuracy is non-negotiable
Scaling complex codebases while maintaining a robust regression test suite