architecture-review

Maps CDD requirements to ADRs and flags architecture gaps and conflicts.

3|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill architecture-review-negentropy-laby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/architecture-review
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill architecture-review-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates completeness and consistency of the project architecture against all CDDs, and produces a traceability matrix that maps every CDD technical requirement to ADRs. It identifies coverage gaps, detects cross-ADR conflicts, and verifies technology compatibility across decisions for both game and general product domains.

Core Features & Use Cases

  • Builds a Requirements Traceability Matrix (RTM) linking CDDs to ADRs and to architecture decisions.
  • Detects coverage gaps, cross-ADR conflicts, and inconsistent technology assumptions across ADRs.
  • Generates a PASS/CONCERNS/FAIL verdict and outputs actionable guidance for stakeholders across game and general product domains.
  • Supports both end-to-end architecture reviews and single-CDD analyses, with optional extension to stories and tests via RTM mode.

Quick Start

Run the architecture-review workflow on your project to generate the report and traceability index.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I check if my project architecture covers all CDD requirements?

To check architecture completeness against CDD requirements, map every technical requirement to its corresponding ADR. This process builds a Requirements Traceability Matrix that highlights coverage gaps and missing architecture decisions across game or general product domains.

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

Detecting cross-ADR conflicts requires mapping multiple architecture decisions against each other to find inconsistent technology assumptions. An automated traceability matrix reviews these decisions across ADRs, identifying contradictions and verifying technology compatibility.

How does a requirements traceability matrix work for ADRs?

A requirements traceability matrix for ADRs links each CDD technical requirement to specific architecture decisions. It outputs a cross-ADR traceability index that visually confirms coverage, detects conflicts, and produces a final PASS, CONCERNS, or FAIL verdict.

Can I run an architecture consistency review for a single CDD?

Yes, you can perform architecture consistency analysis on a single CDD instead of the entire project. The review scales down to validate individual requirement coverage and detect technology compatibility issues within isolated ADRs.

When do I need an architecture review for my game product?

You need an architecture review for your game product when validating that technical CDD requirements are fully traceable to ADRs. It identifies coverage gaps and cross-ADR conflicts early, ensuring technology consistency before downstream development.

What verdicts are generated by an architecture completeness review?

An architecture completeness review generates a PASS, CONCERNS, or FAIL verdict. These verdicts accompany a detailed traceability matrix report, providing actionable guidance to stakeholders for resolving coverage gaps and ADR conflicts.