requirements-to-design

Map PRD requirements to ARD/ADR artifacts and report coverage gaps.

1|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/buenhyden/hy-home.k8s --skill requirements-to-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements-to-design
Source: https://github.com/buenhyden/hy-home.k8s/tree/main/.agents/skills/requirements-to-design
Command: npx skills add https://github.com/buenhyden/hy-home.k8s --skill requirements-to-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connecting and validating PRD requirements with architecture and design artifacts is often manual and error-prone. This Skill provides a structured approach to establish traceability between docs/01.requirements and docs/02.architecture, ensuring alignment from requirements through ARD/ADR decisions in hy-home.k8s.

Core Features & Use Cases

  • Traceability matrixing: automatically links PRD requirements to applicable ARD and ADR artifacts, highlighting gaps.
  • Gap detection and auditing: identifies missing mappings and suggests where ARD or ADR references should be added.
  • Documentation alignment: updates or references related docs to maintain coherence across the SDD lifecycle, from requirements to architecture decisions.

Quick Start

Run a traceability scan to map PRD requirements to ARD/ADR artifacts and generate a coverage report.

Frequently Asked Questions about requirements-to-design

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

FAQPage Schema
How do I map PRD requirements to architecture artifacts for traceability?

To map PRD requirements to architecture artifacts, link and verify traceability between docs/01.requirements and docs/02.architecture. This generates a coverage matrix that highlights alignment and identifies missing ARD or ADR references.

What is a traceability matrix in software architecture documentation?

A traceability matrix in software architecture links PRD requirements to applicable ARD and ADR artifacts. It ensures alignment from requirements through architecture decisions and highlights gaps where mappings are missing.

How do I audit requirements coverage across architecture decision records?

To audit requirements coverage across architecture decision records, run a traceability scan against docs/01.requirements and docs/02.architecture. This reports missing mappings and suggests where ADR references should be added.

Can I automatically create missing ADR artifacts during a traceability audit?

You cannot automatically create missing ADR artifacts during a traceability audit. The process reports gaps and suggests where references should be added, but it does not auto-create architecture artifacts.

Does the traceability scan work with ADRs in a k8s environment?

The traceability scan works with ADRs within the hy-home.k8s environment. It extracts requirements, identifies ARD and ADR references, and builds a coverage matrix across the documentation directories.

Why are my PRD requirements not showing coverage in the architecture docs?

PRD requirements may not show coverage if architecture artifacts lack proper ARD or ADR references. A traceability scan detects these gaps and suggests where mappings should be added to maintain coherence.