Help us improve
Share bugs, ideas, or general feedback.
From aidoc-flow
Validates bidirectional traceability across SDD layers: checks link symmetry, ID format, cumulative tags, coverage, and orphans. Optionally repairs broken links. Use before committing or auditing SDD docs.
npx claudepluginhub vladm3105/aidoc-flow-framework --plugin aidoc-flowHow this skill is triggered — by the user, by Claude, or both
Slash command
/aidoc-flow:trace-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate traceability across all SDD artifacts (BRD → PRD → EARS → BDD → ADR →
Validates cross-document consistency across SDD layers: broken links, orphaned artifacts, duplicate IDs, cumulative-tag gaps, and traceability-matrix completeness. Use before releases or after batch generation.
Validates project documentation: lints formatting and naming, checks broken/orphan links, verifies glossary terms and synonyms, detects contradictions/gaps, audits completeness via /doc:lint, /doc:links, etc.
Verifies V-Model artifact graph integrity: checks dead links, orphan artifacts, backlog completeness, valid references across BA sections, Epics, Features, Success Criteria, ADRs, arc42 sections, PLANs, Backlog, Wayfinder rows, and code. Syntactic default; semantic via agent.
Share bugs, ideas, or general feedback.
Validate traceability across all SDD artifacts (BRD → PRD → EARS → BDD → ADR → SPEC → TDD → IPLAN → Code) and report — or optionally repair — gaps. It checks bidirectional link symmetry, ID-format compliance, cumulative tagging, link and anchor resolution, coverage, and orphans. The framework ships no runtime code: this skill IS the checker, applying the declarative checks below against the governance spec.
Use trace-check when:
Do not use it for code-implementation review, non-SDD documentation, or
in-creation single-document feedback (use ../quality-advisor/SKILL.md).
Given a project_root (default {project_root}/docs/) and optional
artifact_types, strictness_level (permissive / strict (default) / pedantic),
auto_fix, and report_format (markdown / json / text):
docs/<NN>_<X>/ (01_BRD … 08_IPLAN), parse
document IDs from filenames, build an ID → path inventory, flag duplicate IDs
and non-conformant docs/<NN>_<X>/ structure.@brd:…@iplan:/@impl-status: tags in docs and code into a bidirectional
upstream/downstream graph.TYPE-NN; element refs 4-segment
TYPE.NN.SS.xxxx; two-digit zero-padding; valid TYPE; no collisions. Reject
legacy 3-segment IDs and placeholders (TBD/XXX/NNN).can_reference set in framework/registry/LAYER_REGISTRY.yaml; report gaps
and any downstream-tag leakage.#anchor resolves
(markdown H1, YAML id:, feature Scenario:).(matched pairs / total) × 100 (target ≥ 95%).Auto-fix (auto_fix: true): create a timestamped backup first, then repair
relative paths, add missing downstream references, and log changes to revision
history; provide a rollback command. Never invent placeholder IDs.
Quality gates: 100% link resolution and ID compliance, ≥ 95% bidirectional consistency, no orphaned mid-chain artifacts, Traceability section present on every artifact.
Before checking references, read the project adaptation profile
(.aidoc/profile.yaml). Honor active_layers: treat a disabled skippable
layer as absent by design — do not report a missing reference to it (apply
the cascade rule). Ignore any unknown or out-of-surface key.
Authority: framework/governance/ADAPTATION.md.
framework/governance/TRACEABILITY.mdframework/governance/ID_NAMING_STANDARDS.mdcan_reference/downstream):
framework/registry/LAYER_REGISTRY.yamlframework/governance/DOC_GOVERNANCE_CORE.md../doc-flow/SKILL.md · ../adr-roadmap/SKILL.md ·
../quality-advisor/SKILL.md · ../context-analyzer/SKILL.md