architecture-review

Detects PRD-ADR coverage gaps and conflicts, returning a PASS/CONCERNS/FAIL verdict and traceability matrix without modifying files.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill architecture-review-cenconq25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill architecture-review-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies coverage gaps and conflicts between PRD requirements and ADRs across the architecture to ensure architecture decisions align with product goals.

Core Features & Use Cases

  • Traceability matrix generation: maps PRD requirements to ADRs and highlights gaps.
  • Conflict detection: identifies cross-ADR contradictions and coverage gaps.
  • Read-only governance: produces a verdict (PASS/CONCERNS/FAIL) without editing any files, suitable for reviews.

Quick Start

Analyze current PRDs and ADRs in a fresh session to generate a verdict without making changes.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I check PRD requirements traceability to ADRs?

PRD requirements traceability to ADRs is checked by building a matrix that maps product requirements directly to architecture decision records, highlighting coverage gaps. It outputs a structured PASS/CONCERNS/FAIL verdict without modifying any files.

What is the best way to detect cross-ADR conflicts in architecture review?

Architecture review detects cross-ADR conflicts by analyzing all ADR markdown files to identify contradictions between architecture decisions. It flags these conflicts and reports them alongside coverage gaps in a final structured verdict.

Can I audit architecture health without modifying my repository files?

You can audit architecture health in a strict read-only mode that analyzes architecture markdown, ADR files, and PRDs without modifying any files. This governance approach produces a safe PASS/CONCERNS/FAIL verdict suitable for formal reviews.

What files do I need for architecture and ADR coverage gap analysis?

Architecture and ADR coverage gap analysis requires PRD files in design/prd, ADR markdown files in docs/architecture, architecture.md, systems-index.md, framework references, and architecture-registry.yaml to map traceability accurately.

How do I generate an architecture traceability matrix from PRDs?

Generating an architecture traceability matrix from PRDs involves parsing requirements from design documents and mapping them directly to corresponding ADRs. The output matrix clearly highlights unmet requirements and conflicting architecture decisions.