Skill

vcsdd-trace

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.

code-quality

testing

npx claudepluginhub sc30gsw/vcsdd-claude-code --plugin vcsdd

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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.

SKILL.md

Similar Skills

vcsdd-traceability

Creates 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.

vcsdd

traceability-check

104

Verifies bidirectional traceability from requirements to code to tests. Scans .aiwg/requirements/, code files, tests, and commit messages for ID references like UC-*, REQ-*. Builds matrix, identifies coverage gaps, orphans, and untested code.

sdlc

beads-schema

Provides Beads (bd CLI) reference for issue types, statuses, priorities, dependencies, hierarchies, and commands. Use when creating, editing, or managing git-backed beads issues via bd.

4 tools

essentials

Stats

Stars16

Forks0

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

BEAD-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

What

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.

When

Run at any time to understand why a piece of code exists or to check spec-to-test-to-impl coverage.

How

Parse argument: bead ID (BEAD-NNN) or external ID (REQ-001, PROP-001, etc.)
If external ID: find bead by externalId field
Load traceability chain: BFS traversal from root bead

Display formatted chain:

BEAD-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

Show chain completeness warnings: orphan beads, spec reqs without tests, etc.

Examples

/vcsdd-trace BEAD-001
/vcsdd-trace REQ-001
/vcsdd-trace PROP-002
/vcsdd-trace --check-completeness    # validate full chain integrity