traceability-render

Render module traceability documents with REQs, DESs, TESTs, and code anchors.

41|6|Updated Jul 12, 2025
One-click install
npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill traceability-render
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: traceability-render
Source: https://github.com/SteveGJones/ai-first-sdlc-practices/tree/main/plugins/sdlc-assured/skills/traceability-render
Command: npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill traceability-render

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewers and auditors need a concise, human-friendly view of a module's traceability. This skill aggregates REQs, DESs, TESTs, and code locations with anchors into a single, navigable Markdown document, plus a module-dependency graph represented as a Markdown edge-list.

Core Features & Use Cases

  • Generates a module-scoped traceability document that includes REQs, DESs, TESTs, and code locations with anchors.
  • Produces a Markdown-formatted dependency graph (edge-list) for quick impact analysis.
  • Supports auditing workflows by providing a reproducible, idempotent output written to docs/traceability.

Quick Start

Provide the module-id (e.g., P1.SP1.M1) to render its traceability document.

Frequently Asked Questions about traceability-render

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a module traceability document in markdown for requirements and tests?

To generate a module traceability document, provide a module-id and the skill reads project registries and code indices, filters to the target module, and renders REQs, DESs, TESTs, and code locations into a single navigable markdown file.

What is module-level traceability and when do I need a dependency graph for reviews?

Module-level traceability maps requirements, designs, tests, and code locations to verify completeness and impact. You need it during reviews or audits where a module-dependency graph is required to analyze structural relationships.

Can I render a dependency graph as a markdown edge-list for impact analysis?

Yes, you can render a dependency graph as a markdown edge-list. The skill produces this graph alongside the traceability document to enable quick impact analysis for the target module.

How do I create an idempotent traceability report for software audits?

You create an idempotent traceability report by running the skill with a target module-id. It reproducibly aggregates project registries and writes the generated markdown file to the docs/traceability directory.

Does module traceability rendering work without external dependencies?

Yes, module traceability rendering works without external dependencies. The skill requires no listed dependencies and operates by reading existing project registries and code indices to output the markdown document.