skills.rest
craigtkhill
craigtkhillCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-test-driven-development

Automate spec-first test-driven development for new features.

Updated Nov 17, 2025
Search Tags:#workflow#testing#quality assurance#software development#requirements#implementation#Spec-TDD
One-click install
npx skills add https://github.com/craigtkhill/atui-tools --skill spec-test-driven-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-test-driven-development
Source: https://github.com/craigtkhill/atui-tools/tree/main/skills/spec-test-driven-development
Command: npx skills add https://github.com/craigtkhill/atui-tools --skill spec-test-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent development processes and unclear requirements by enforcing a strict Specification-Test-Driven Development (Spec-TDD) workflow. It ensures that features are well-defined, thoroughly tested, and correctly implemented, reducing bugs, rework, and project delays.

Core Features & Use Cases

  • Structured Workflow Enforcement: Guides you through writing specifications, then tests, then implementation, in a disciplined, sequential manner.
  • Requirement Traceability: Links implementation directly back to approved specifications, ensuring all requirements are met and documented.
  • Quality Assurance: Integrates test execution and pre-commit hooks to guarantee code quality and prevent regressions before marking work as complete.
  • Use Case: When starting any new feature, use this skill to ensure you first define the user story and requirements, then write tests, then implement the code, and finally verify with tests and pre-commit checks, leading to higher quality and more predictable outcomes.

Quick Start

Start a new feature. Use the spec-test-driven-development skill to guide you through the entire process, beginning with writing the specification.

Frequently Asked Questions about spec-test-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement spec-driven development for new features?▼

Spec-driven development starts with writing a specification using user story format (As a... I want... So that...), then designing unit and acceptance tests, and finally implementing code incrementally. This workflow ensures requirements are clear before coding begins, reducing rework and bugs.

What's the difference between test-driven development and spec-test-driven development?▼

Spec-TDD adds a specification phase before test design, creating explicit requirement traceability. Traditional TDD jumps to tests; Spec-TDD documents the 'why' and 'what' through specifications first, linking implementation directly back to approved requirements.

How do I ensure quality assurance in a test-driven workflow?▼

Spec-TDD integrates test execution and pre-commit hooks to catch regressions before code is committed. Tests validate that implementation matches specifications, and automation gates prevent incomplete or untested work from being merged.

Can I use spec-test-driven development with existing codebases?▼

Spec-TDD works best when starting new features or functionality. For existing code, apply it to new requirements and enhancements while maintaining backward compatibility; the workflow enforces clarity on what's being added and why.

What test formats does spec-test-driven development support?▼

Spec-TDD supports both unit tests and acceptance tests with defined naming conventions and scenario formats. Tests map to specifications through tracking markers, enabling full traceability from requirements through test execution to implementation.

Do I need approval steps before implementing after writing tests?▼

Yes, Spec-TDD includes approval workflows after specification and testing phases. Pre-commit hooks and approval gates verify that specifications are met before marking work complete, ensuring consistency across team development practices.

Related Skills

Explore More Software Engineering Skills→
AsiaOstrichAsiaOstrich
70

atdd-assistant

Guide Acceptance Test-Driven Development workflows for defining and validating user stories.

Community
Intermediate
corbat-techcorbat-tech
1

worktree-finish

Merges a verified Git worktree branch and cleans it up afterward.

Official
Advanced
HomericIntelligenceHomericIntelligence
6

verification

Run pytest, mypy, ruff, and pre-commit checks before declaring completion.

Official
Intermediate
ZzAveZzAve

tdd

Guide Test-Driven Development with behavior-focused tests and minimal implementation.

Community
Intermediate