architecture-review

Assess sprint architecture updates for consistency and risk exposure.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/busboom-software-studio/design-trainer --skill architecture-review-busboom-software-studio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/busboom-software-studio/design-trainer/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/busboom-software-studio/design-trainer --skill architecture-review-busboom-software-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams verify that sprint architecture updates align with the existing system, ensuring consistency, quality, and reduced risk.

Core Features & Use Cases

  • Read the current architecture in docs/clasi/architecture/.
  • Read the sprint's architecture update (architecture-update.md).
  • Compare documented architecture with the actual codebase to identify drift.
  • Produce a verdict based on Version Consistency, Codebase Alignment, Design Quality, Anti-Pattern Detection, and Risks.

Quick Start

Review the latest architecture-update.md and compare it against docs/clasi/architecture to ensure alignment.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I check sprint architecture updates for consistency with the existing system?▼

Check sprint architecture consistency by comparing the architecture-update.md against documented architecture in docs/clasi/architecture. The review cross-checks the codebase for alignment, evaluates version consistency, design quality, anti-patterns, and deployment risks, then surfaces a formal verdict.

What is architecture drift detection and how does it work during a sprint?▼

Architecture drift detection compares documented architecture against the actual codebase to identify misalignment. It evaluates version consistency, codebase alignment, design quality, anti-patterns, and risks, producing a formal verdict to ensure sprint updates maintain system integrity.

Do I need documented architecture in docs/clasi/architecture to review sprint updates?▼

Yes, you need documented architecture in docs/clasi/architecture and sprint updates in architecture-update.md. The review requires cross-checking the codebase against these files to assess version consistency, codebase alignment, design quality, anti-patterns, and deployment risks.

What's the best way to assess deployment risks and anti-patterns in architecture updates?▼

Assess deployment risks and anti-patterns by comparing architecture-update.md against docs/clasi/architecture and cross-checking the codebase. The review evaluates design quality, detects anti-patterns, identifies deployment risks, and produces a formal verdict on sprint architecture consistency.

Why does my architecture review show codebase alignment issues?▼

Architecture reviews show codebase alignment issues when the actual codebase drifts from documented architecture in docs/clasi/architecture. Comparing against architecture-update.md identifies version inconsistencies, design quality degradation, anti-patterns, and deployment risks that cause formal verdict failures.

Can I review architecture updates for design quality without cross-checking the codebase?▼

No, reviewing architecture updates requires cross-checking the codebase for alignment. The review evaluates version consistency, codebase alignment, design quality, anti-patterns, and deployment risks by comparing architecture-update.md against docs/clasi/architecture and the actual codebase.