traceability
/traceability
WAY 14 — requirements traceability matrix for a user story (each acceptance criterion) or a test folder written from plain text (each R-NN requirement) → the tests covering it → their latest result → open bugs. Use when the user says "trace it", "traceability", "is #148 covered", "coverage of SHOP-148", "trace it <folder>".
- Author
- ghassenazzouz ↗
- Repository
- claude-qa-agent ↗
- Licence
- MIT
- Last repository change
- 18.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
WAY 14 — requirements traceability matrix for a user story (each acceptance criterion) or a test folder written from plain text (each R-NN requirement) → the tests covering it → their latest result → open bugs. Use when the user says "trace it", "traceability", "is #148 covered", "coverage of SHOP-148", "trace it <folder>".
Triggers from the description
Original author description
WAY 14 — requirements traceability matrix for a user story (each acceptance criterion) or a test folder written from plain text (each R-NN requirement) → the tests covering it → their latest result → open bugs. Use when the user says "trace it", "traceability", "is #148 covered", "coverage of SHOP-148", "trace it <folder>".
How it works
- Step 1: Gather inputs
- Phase 1: Build the matrix
- Phase 2: Classify each AC
- Phase 3: Report
SKILL.md preview
--- name: traceability description: 'WAY 14 — requirements traceability matrix for a user story (each acceptance criterion) or a test folder written from plain text (each R-NN requirement) → the tests covering it → their latest result → open bugs. Use when the user says "trace it", "traceability", "is #148 covered", "coverage of SHOP-148", "trace it <folder>".' --- # WAY 14 — Traceability Matrix ## Step 1: Gather inputs One or more story refs, or test folders whose requirements are plain text (`trace it password-reset-2026-10-13`, the folder name under `qa-artifacts/test-cases/`). At least one is required. ## Phase 1: Build the matrix For each story: 1. **Requirements** (IDs per `requirements-analysis` §3): - Story ref: `issue.get`, then parse the Acceptance Criteria table (`AC-01 … AC-nn`, title, priority) from the `user-story-format` body. If the story has no ACs, use the `## Requirements` table (`R-NN`) of the test folders whose index has `**Source:** <ref>`. If there's neither, say so and suggest `enhance us <ref>` (WAY 6) first - Folder: the `## Requirements` table of its index `.md` (`**Source:** text`). If it has none, its tests predate R-NN: list them all as untraced and suggest `write it` to re-derive - A story that has ACs while some of its folders cite `R-NN`: trace against the ACs, and list those tests as untraced with "re-trace with `write it <ref>`" 2. **Tests:** Grep `qa-artifacts/test-cases/**` for `**Source:** <ref>` (or take the given folder). In those folders, read each `Test#<nn>.md` `**Covers:**` line and the `# Test#<nn> | AC-<NN>` / `R-<NN>` comments in the `.feature` 3. **Latest result:** for each test, take the newest `runs/*/results.json` that contains its spec, and its status there (plus the run date) 4. **Bugs:** `issue.list` with label `bug` and the test folder name as search text (bug bodies cite the test path), plus bugs that reference the story ref. Keep the open ones ## Phase 2: Classify each AC | Status | Meaning | |---|---| | 🟢 covered — passing | ≥1 test, all passing in their latest run | | 🔴 covered — failing | ≥1 test failing, or an open bug | | 🟡 covered — not run | tests exist, no run found | | ⚪ untested | no test mentions this AC | Tests marked `**Covers:** untraced` are listed separately. They test something the story doesn't state, which is a hint the story is incomplete. ## Phase 3: Report Save `./qa-artifacts/traceability/<ref-or-folder>-<YYYY-MM-DD>.md` (for a folder, the AC column holds `R-NN` and the header says `Requirements: plain text, IDs derived`): ```markdown # Traceability — <ref> <story title> **Coverage:** 5/7 ACs tested · 4 passing · 1 failing · 2 untested | AC | Title | Priority | Tests | Latest result | Open bugs | Status | |---|---|---|---|---|---|---| | AC-01 | Apply a valid code | must | Test#01, Test#02 | ✅ ✅ (2026-10-09) | — | 🟢 | | AC-04 | Expired code rejected | must | — | — | — | ⚪ | **Untraced tests:** Test#07 (checks currency rounding: not in any AC) --- 🤖 _Generated by DevOps QA Agent — review before acting on this._ ``` Print the summary. Ask the user before posting it as a comment on the story (a folder has no story to post on). For untested `must` requirements, offer `write it <ref>` (WAY 4).
Versions
The database has no other skills named traceability.
Database snapshot: 13.11.2026 · package version e51d8ca17b16 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90bmad-testarch-trace
Generate traceability matrix and quality gate decision. Use when the user says "lets create traceability matrix" or "I want to analyze test coverage - 100traceability-matrix
Create a requirements traceability matrix linking requirements to design, test, and delivery. Use when the user says "traceability matrix", "RTM", "requirements traceability", "link requirements to tests", "trace requirements", "coverage matrix", "are all requirements tested",… - 100ac-coverage
[UDS] Analyze AC-to-test traceability and generate requirement-level coverage reports. Use when: auditing which acceptance criteria have tests, building a traceability matrix from a SPEC file, finding uncovered AC before release. Not for: code-level line/branch/function coverage… - 90bmad-tea-trace
Generate traceability matrix and quality gate decision. Use when the user says "lets create traceability matrix" or "I want to analyze test coverage - 90esp32-requirement-test-traceability
Use when designing, reviewing, debugging or validating requirement test traceability for ESP32 firmware; apply target-specific constraints, failure analysis and measurable verification before release. - 100requirements-test-cases
Step 4 of the requirements workflow — turns a requirement and its acceptance criteria into concrete, executable test cases QA can run, and links requirements → stories → tests in a traceability matrix so nothing ships untested. Triggers whenever a user says things like "write…