Where does this skill save specification files?

Following the principle of locality of behavior, specifications are saved as SPEC.md files in the same directory as the feature code or in a dedicated feature-specific subdirectory.

What do the [U][A][X][O] markers represent?

These markers track implementation status: [U] for Unit Tests, [A] for Acceptance Tests, [X] for Implemented code, and [O] for Not Yet Implemented.

Why does the skill insist on atomic requirements?

Atomic requirements ensure that each entry tests exactly one specific thing. This prevents complexity and allows each requirement to map clearly to a single test or a small set of closely related tests.

What is the STDD workflow?

STDD stands for Spec-Test-Driven Development. It is a three-step process: first you write the specification, then you write the tests based on those requirements, and finally you implement the code to pass the tests.

STDD Specification Architect

Name: STDD Specification Architect
Author: craigtkhill

bycraigtkhill

Security & Testing

Standardizes the creation of SPEC.md files to ensure atomic, user-centric requirements for Spec-Test-Driven Development workflows.

About

This skill streamlines the initial phase of the Spec-Test-Driven Development (STDD) process by enforcing a strict domain-specific language for requirement gathering. It ensures that specifications are maintained close to the code they describe, uses standardized requirement tracking codes (U/A/X/O), and focuses exclusively on user-facing features rather than internal implementation details. By guiding the AI to write atomic, testable requirements and Given/When/Then scenarios, it provides a rigorous foundation for subsequent automated testing and implementation phases.

Key Features

Implements user story patterns using the As-a/I-want/So-that framework
0 GitHub stars
Ensures atomic requirement definition for simplified test mapping
Enforces standardized SPEC.md structure and hierarchical formatting
Generates Given/When/Then scenarios for end-to-end behavior validation
Tracks implementation status via unit, acceptance, and code-complete markers

Use Cases

Defining new feature requirements before starting the TDD coding cycle
Standardizing project documentation across distributed engineering teams
Auditing existing features to map user requirements to specific test cases

About

Key Features

Implements user story patterns using the As-a/I-want/So-that framework
0 GitHub stars
Ensures atomic requirement definition for simplified test mapping
Enforces standardized SPEC.md structure and hierarchical formatting
Generates Given/When/Then scenarios for end-to-end behavior validation
Tracks implementation status via unit, acceptance, and code-complete markers

Use Cases

Defining new feature requirements before starting the TDD coding cycle
Standardizing project documentation across distributed engineering teams
Auditing existing features to map user requirements to specific test cases