sdlc-trace

Audits traceability across specifications, code, and tests by recomputing scenario hashes and rebuilding the trace index.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/juartaurus98/codebase --skill sdlc-trace-juartaurus98
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-trace
Source: https://github.com/juartaurus98/codebase/tree/main/.claude/skills/sdlc-trace
Command: npx skills add https://github.com/juartaurus98/codebase --skill sdlc-trace-juartaurus98

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Specifications, implementations, and tests drift apart as a project evolves, leaving orphan code, untested behavior, and stale specs that nobody notices until something breaks. This Skill enforces traceability by auditing every use case, scenario, implementation tag, and test, then reporting one finding per violation. ## Core Features & Use Cases - Traceability Audit: Verifies that every use case has a feature file, every scenario has a tagged implementation, and every implementation has a verifying test, applying rules T1–T9 with fixed severities. - Stale Spec Detection: Recomputes scenario spec hashes to detect when code and tests were built against an outdated specification (T8 STALE-SPEC), and flags AI prompt versions lacking eval sets or recorded runs (T9 EVAL-GAP). - Index Rebuild and Findings: Regenerates the derived TSV trace index wholesale, applies time-boxed waivers, and writes one routed finding per violation so downstream gates can act on them. - Use Case: After a sprint of changes, run the audit on a feature ID to discover that two scenarios lost their test coverage and one spec was edited after its implementation, then route each finding to the right remediation step. ## Quick Start Ask the AI to run the traceability audit for a specific feature ID, or for the whole repository, and report violations with the coverage summary.

Frequently Asked Questions about sdlc-trace

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

FAQPage Schema
How do I audit traceability between specs, code, and tests?▼

Run the trace audit with a feature ID or no argument for the whole repository. It delegates a read-only scan to match scenario tags across feature files, implementations, and tests, then reports violations T1–T9 with severities and a coverage summary.

How to detect stale specifications after code changes?▼

The audit recomputes each scenario's spec_hash and compares it to the stored value. A mismatch is reported as T8 STALE-SPEC, meaning the implementation and tests were built against a different specification and downstream artifacts are suspect.

Can I suppress a traceability violation temporarily?▼

Yes, by adding a row to the trace waivers file with an owner and an expiry date. Expired waivers are not honored and are reported as major violations; waivers without an expiry date are not allowed.

Does the trace audit fix missing tags automatically?▼

No. The audit is read-only over the repository and never adds or fixes trace tags, creates waivers, or infers links from similar filenames. Missing tags are reported as findings for the code or test generation steps to fix.

What happens when a prompt version has no eval set?▼

It is reported as T9 EVAL-GAP and routed to techdoc. A prompt version in the registry without an eval set or recorded run means its quality has never been measured, which the audit treats as a traceability violation.