Skill: traceability-render
SkillDocs & knowledgeRender module-scoped human-readable traceability for a single module — REQs, DESs, TESTs, code locations with anchor links, plus the module-dependency graph as a markdown edge-list.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Skill: traceability-render skill
What this skill tells your AI
The instructions your AI receives, as published by stevegjones/ai-first-sdlc-practices in skills/traceability-render/SKILL.md and read by ahel’s review.
Use this skill when a reviewer or auditor needs a human-readable view of one module's traceability. Produces a markdown document with anchors that resolve in any markdown renderer, no Sphinx required.
Inputs
<module-id>— e.g.,P1.SP1.M1. If the project uses default decomposition, justM1is accepted.
Steps
-
Validate the module exists. Read
programs.yaml; confirm the module is declared. -
Load the registry. Read
library/_ids.mdandlibrary/_code-index.md. -
Filter to the module. Keep only IDs whose module assignment matches.
-
Render the module scope. Use
render_module_scope. -
Render the dependency graph. Walk source-file imports to derive the
actual_edges. Userender_module_dependency_graph. -
Concatenate scope + dependency graph into one document.
-
Write to
docs/traceability/<module-id>.md. Idempotent. -
Print the path of the rendered document.
Done criteria
- Document written.
- Contains REQs, DESs, TESTs, code, orphan code, dependency graph.
- Idempotent.
Signals
- GitHub stars
- 41
- Forks
- 6
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
traceability-render- Source
- github.com/stevegjones/ai-first-sdlc-practices