Stats
Actions
Tags
From vcsdd
Traces full VCSDD bead traceability chains via Chainlink graph BFS traversal, displaying connected specs, tests, implementations, proofs, findings with status, paths, and completeness warnings. Use to check spec-to-test-to-impl coverage or code origins.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vcsdd:vcsdd-traceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Displays the full traceability chain for a given bead, traversing the Chainlink graph (BFS) to show all connected spec requirements, test cases, implementations, findings, and proof obligations.
Displays the full traceability chain for a given bead, traversing the Chainlink graph (BFS) to show all connected spec requirements, test cases, implementations, findings, and proof obligations.
Run at any time to understand why a piece of code exists or to check spec-to-test-to-impl coverage.
externalId fieldBEAD-001 [spec-requirement] active
External: REQ-001
Path: specs/behavioral-spec.md#REQ-001
Connected chain:
+-- BEAD-003 [test-case] passing
| External: TEST-001
| Path: tests/test_parser.py::test_empty
| +-- BEAD-005 [implementation] implemented
| Path: src/parser.py:42-58
+-- BEAD-010 [verification-property] proved
External: PROP-001
Path: verification/proof-harnesses/parser_empty.py
/vcsdd-trace BEAD-001
/vcsdd-trace REQ-001
/vcsdd-trace PROP-002
/vcsdd-trace --check-completeness # validate full chain integrity
npx claudepluginhub sc30gsw/vcsdd-claude-code --plugin vcsddCreates and manages VCSDD Chainlink beads for traceability across spec-requirements, verification-properties, test-cases, implementations, and adversary-findings; supports linking, traversal via /vcsdd-trace, and completeness validation.
Navigates bidirectional traceability links in sphinx-needs projects between requirements, specifications, implementations, tests, and code from any need ID.
Creates, updates, or inspects requirements traceability matrices linking requirements, design, tasks, tests, PRs, commits, releases, and evidence gaps across SDLC artifacts.