What happens when a specification requirement changes?

The skill enforces rules where paragraph IDs are never reused. New features get new IDs, and modifications are noted in a history block to maintain a clear audit trail for the system's evolution.

How does spec-tracing help with test coverage?

By tagging tests with @trace markers, the skill allows you to run scripts that identify which specification paragraphs lack corresponding tests, ensuring 100% requirement validation.

What is the purpose of the [SPEC-XX.YY] ID format?

The format provides a unique, immutable identifier for every normative requirement in a specification, allowing developers to link specific lines of code or tests directly to the requirement they fulfill.

Can I use this skill with any programming language?

Yes, the spec-tracing pattern is language-agnostic. It uses standard comment blocks (e.g., //, #, /** */) to embed traceability markers in source code across all major languages.

Specification Tracing & Coverage

Name: Specification Tracing & Coverage
Author: rand

byrand

•

安全与测试

Enforces rigorous software development by linking normative specifications to implementation and test suites using unique paragraph IDs.

The spec-tracing skill implements a disciplined development workflow by enforcing a 1-to-1 mapping between system requirements and their technical implementations. It provides a standardized framework for authoring specifications with RFC 2119 terminology, assigning unique traceable IDs to normative statements, and verifying coverage across source code and test files. This skill is essential for teams requiring high-assurance software, clear audit trails, or automated verification that every design requirement has been correctly implemented and validated through testing.

主要功能

01Cross-language implementation traceability via @trace comments

02Strict modification rules to prevent ID reuse and maintain version history

03Standardized paragraph ID formatting for granular requirement tracking

042 GitHub stars

05RFC 2119 normative language enforcement (MUST, SHALL, SHOULD)

06Automated coverage verification patterns for specs and tests

使用场景

01Maintaining large documentation sets where code must strictly adhere to design

02Building safety-critical or high-compliance software requiring strict audit trails

03Automating the verification of requirement coverage in CI/CD pipelines

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add rand/disciplined-process-plugin spec-tracing

For use in Claude.ai and ChatGPT

Download Skill