spex-write-tests

Map spec scenarios to corresponding tests for spec.md traceability.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/dmayerdesign/spex --skill spex-write-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spex-write-tests
Source: https://github.com/dmayerdesign/spex/tree/main/.claude/skills/spex-write-tests
Command: npx skills add https://github.com/dmayerdesign/spex --skill spex-write-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure every behavior described in the spec is covered by tests, promoting traceability between spec.md and test implementations.

Core Features & Use Cases

  • Map each spec scenario to a corresponding test to verify behavior and ensure alignment between spec and tests.
  • Review and augment test suites to close gaps where scenarios lack coverage, supporting TDD workflows.
  • Name tests after scenarios and maintain fast, independent test cases that reflect the spec structure.

Quick Start

Provide the spec and existing code context and I will generate tests aligned to each scenario for your project.

Frequently Asked Questions about spex-write-tests

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

FAQPage Schema
How do I generate tests from a specification document?▼

Test traceability between a spec and test suite is achieved by mapping each spec scenario to a corresponding test, enforcing frontmatter-driven discovery and naming tests directly after scenarios.

How do I ensure traceability between my spec.md and test suite?▼

Test traceability between a spec and test suite is achieved by mapping each spec scenario to a corresponding test, enforcing frontmatter-driven discovery and naming tests directly after scenarios.

How do I close test coverage gaps for edge-case scenarios in TDD?▼

Closing test coverage gaps for edge-case scenarios involves reviewing and augmenting existing test suites to add missing tests, maintaining a one-behavior-per-test discipline within your TDD workflow.

Do I need a specific test framework to map spec scenarios to tests?▼

No specific test framework is required, as the skill aligns generated tests with your project's common conventions for test structure and execution rather than enforcing a dependency.

What is the best way to structure tests for spec scenarios?▼

The best way to structure tests for spec scenarios is maintaining a one-behavior-per-test discipline, naming tests after scenarios, and keeping fast, independent test cases that reflect the spec structure.