blueprint-sdd-traceability-keeper

Verify requirement traceability across specifications, code, and tests.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/sbonoc/stackit-platform-blueprint --skill blueprint-sdd-traceability-keeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint-sdd-traceability-keeper
Source: https://github.com/sbonoc/stackit-platform-blueprint/tree/main/.agents/skills/blueprint-sdd-traceability-keeper
Command: npx skills add https://github.com/sbonoc/stackit-platform-blueprint --skill blueprint-sdd-traceability-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables teams to maintain and verify comprehensive traceability from requirements through specifications, implementation, tests, and documentation, helping identify gaps and prevent overlooked coverage.

Core Features & Use Cases

  • Traceability Verification: Cross-check requirements, code, tests, and docs for completeness.
  • Gap Detection: Identify orphaned requirements and undocumented behaviors to ensure full coverage.
  • Quality Assurance: Support pre-merge and hardening reviews by validating traceability and evidence links.
  • Use Case: During development, verify that every requirement is linked to tests and documentation, ensuring compliance and reducing risk before release.

Quick Start

Use the traceability skill to inspect your project, verifying that all requirements and related artifacts are properly linked and documented.

Frequently Asked Questions about blueprint-sdd-traceability-keeper

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

FAQPage Schema
How do I verify requirement traceability from specifications to tests?

Requirement traceability is verified by cross-checking links between specifications, code, tests, and documentation to identify gaps. This Skill maintains a traceability matrix to validate complete coverage and prevent overlooked requirements.

What is requirement gap analysis in software quality assurance?

Requirement gap analysis in quality assurance is the detection of orphaned requirements and undocumented behaviors. It ensures full coverage by validating that all project artifacts are properly linked and documented before release.

How do I detect orphaned requirements during development?

Detect orphaned requirements by applying link validation against your traceability matrices to find unconnected specifications. This identifies undocumented behaviors and missing test coverage to ensure robust project integrity.

Can I use traceability verification for pre-merge compliance audits?

Traceability verification supports pre-merge and hardening reviews by validating evidence links for compliance audits. It checks that requirements, code, tests, and documentation are completely linked to reduce risk before release.

What is the best way to maintain a traceability matrix for code and tests?

Maintaining a traceability matrix is best done by systematically mapping requirements to code and tests, then running link validation to detect gaps. This approach ensures robust project integrity and supports ongoing development workflows.