architecture-review

Reviews stories or entire systems against 8 architecture dimensions and reports risks and tech debt.

2|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Vibecoder79/jarvis --skill architecture-review-vibecoder79
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/Vibecoder79/jarvis/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/Vibecoder79/jarvis --skill architecture-review-vibecoder79

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Architecture reviews often happen only after something breaks, or degrade into gut-feel judgments. This Skill turns architecture review into a routine checkpoint by forcing a complete read of ARCHITECTURE_DESIGN.md (all sections and ADRs) before any assessment, then evaluating changes against 8 defined dimensions. ## Core Features & Use Cases - Story Review (Mode A): Evaluates a single story or planned change against relevant architecture dimensions before implementation, producing per-dimension status (OK / Warning / Critical), findings, and recommendations. - System Review (Mode B): Audits the entire system across all 8 dimensions, identifying strengths, top risks, tech debt level, and recommended backlog issues. - Enforced documentation checklist: Requires reading sections 1-8 and every ADR of the architecture design document before judging, tying every finding to a concrete design decision. - Use Case: Before sending a story about a new Kafka consumer retry mechanism to implementation, run a Story Review to catch missing exponential backoff and get a concrete recommendation referencing existing ADR precedents. ## Quick Start Ask the assistant to run an architecture review on the current story by saying "/architecture-review" or "does this change fit architecturally?".

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I run an architecture review on a story before implementation?▼

Trigger Story Review mode with "/architecture-review" or phrases like "does this fit architecturally". The skill reads ARCHITECTURE_DESIGN.md completely, maps the change to affected components, evaluates relevant dimensions, and outputs status, findings, and recommendations per dimension.

What architecture dimensions does a system review check?▼

A system review checks 8 dimensions: Reliability, Data Integrity, Security, Performance, Observability, Maintainability, Cost Efficiency, and Signal Quality. Dimensions 7 and 8 are domain-customizable at bootstrap time to match what your project actually cares about.

What is the difference between Story Review and System Review modes?▼

Story Review evaluates one story or planned change against only the relevant dimensions before implementation. System Review audits the whole system across all 8 dimensions, producing strengths, top risks, a tech debt score, and recommended backlog issues.

Why does the skill require reading the full architecture document first?▼

The enforced read-first rule prevents reviews from degrading into gut-feel judgments. By requiring all sections 1-8 and every ADR to be read, each finding ties back to a concrete ADR or documented design decision rather than assumptions.

When should I not use an 8-dimension architecture review?▼

Skip the full review for trivial changes with no architectural impact, since not every change touches all 8 dimensions. The skill itself evaluates only relevant dimensions per change, so very small fixes may be better served by a lightweight code review.