architecture-review

Name: architecture-review
Availability: InStock
Author: NuoYan

Validate architectural coverage and consistency against game design requirements and ADRs.

47|12|Updated Jun 14, 2026

Search Tags:#requirements traceability #dependency analysis #ADR #architecture review #conflict detection #GDD #engine compatibility

Ready to run

npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill architecture-review-nuoyanruoshui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/architecture-review
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill architecture-review-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies gaps, conflicts, dependency issues, and engine compatibility risks between game design requirements and architectural decisions before implementation begins.

Core Features & Use Cases

Requirements Traceability: Maps technical requirements from GDDs to ADRs and optionally extends the chain to production stories and tests.
Architecture Consistency Audits: Detects cross-ADR conflicts involving ownership, integration contracts, performance budgets, dependencies, state management, and architectural patterns.
Engine Compatibility Review: Checks engine versions, deprecated APIs, post-cutoff API assumptions, and specialist findings against the project’s pinned engine.
Use Case: Run a full review to determine whether all game systems are architecturally covered, identify blocking gaps, and produce a prioritized implementation order and verdict.

Quick Start

Run the architecture review skill with no argument for a complete requirements, consistency, dependency, and engine compatibility audit.

Frequently Asked Questions about architecture-review

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

FAQPage Schema

How do I check requirements traceability from a GDD to architecture decisions?▼

An architecture consistency audit detects cross-ADR conflicts involving ownership, integration contracts, performance budgets, dependencies, state management, and architectural patterns across your project's decisions.

How do I detect conflicts between architectural decision records?▼

What is the best way to validate engine compatibility against deprecated APIs?▼

You need project GDDs, ADRs, engine reference documents, and technical preferences. Production stories and tests are optional inputs for extending the requirements traceability chain.

Do I need ADRs and engine reference documents to run an architecture review?▼

You need project GDDs, ADRs, engine reference documents, and technical preferences. Production stories and tests are optional inputs for extending the requirements traceability chain.

How do I run a full architecture audit for game systems coverage?▼

Run the architecture review with no arguments to execute a complete audit covering requirements traceability, consistency checks, dependency analysis, and engine compatibility, producing a prioritized implementation order and verdict.

What limitations should I expect when mapping GDD requirements to ADRs?▼

The review relies on the completeness of provided GDDs, ADRs, and engine reference documents; missing or outdated technical preference documents will limit the accuracy of dependency analysis and cross-ADR conflict detection.