Architecture Review

Analyze usage patterns and map current architecture to evaluate pivot costs.

11|Updated Jun 19, 2013

Search Tags:#architecture #code review #system design #software development #technical debt #greenfield

Ready to run

npx skills add https://github.com/MadBomber/experiments --skill architecture-review-madbomber

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Architecture Review
Source: https://github.com/MadBomber/experiments/tree/main/ai_misc/skills/architecture-review
Command: npx skills add https://github.com/MadBomber/experiments --skill architecture-review-madbomber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents costly architectural mistakes by forcing a deep re-evaluation of technology choices before embarking on major new features, ensuring the existing stack is the right foundation.

Core Features & Use Cases

Greenfield Questioning: Challenges existing technology choices by asking "If building today, would I choose the same stack?"
Anti-Pattern Detection: Identifies common issues like "bridge-to-a-bridge" architectures and sunk cost fallacies.
Use Case: Before adding a new mobile platform to an existing desktop application, use this skill to determine if the current backend and data synchronization strategy is still appropriate or if a complete re-architecture is needed.

Quick Start

Use the architecture review skill to evaluate adding real-time collaboration to our Electron app.

Frequently Asked Questions about Architecture Review

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

FAQPage Schema

How do I evaluate if my existing technology stack is the right foundation before building a new feature?▼

To evaluate your technology stack before building a new feature, conduct an architectural review that challenges current choices by asking if you would choose the same stack if building today. This process maps current usage patterns and identifies forcing functions for re-architecture to prevent incremental technical debt accumulation.

When do I need to consider a complete system design re-architecture instead of incremental updates?▼

You need a complete system design re-architecture when an architectural review identifies anti-patterns like the sunk cost fallacy or bridge-to-a-bridge architectures. If adding new capabilities like real-time collaboration to an Electron app forces stack re-evaluation, pivoting avoids costly technical debt accumulation.

How do I document architectural decisions and evaluate pivot costs for new software development?▼

To document architectural decisions and evaluate pivot costs for software development, analyze usage patterns and map the current architecture against greenfield design considerations. This process calculates the trade-offs of re-architecture versus adapting the existing stack, ensuring risky technical debt is mitigated before major features are built.

What is greenfield questioning and how does it prevent technical debt in system design?▼

Greenfield questioning is an architectural review technique that challenges existing technology choices by asking if you would select the same stack if starting from scratch today. It prevents technical debt by exposing sunk cost fallacies and identifying when a forcing function requires a complete system re-architecture.

Can I use an architecture review to assess adding a new mobile platform to an existing desktop application backend?▼

Yes, you can use an architecture review to assess adding a new mobile platform to an existing desktop application. It evaluates whether your current backend and data synchronization strategy remains appropriate or if a complete re-architecture is required to support the new platform without accumulating technical debt.

What are the limitations of incremental updates versus a full re-architecture for legacy system design?▼

The limitation of incremental updates in legacy system design is the risk of accumulating technical debt through anti-patterns like bridge-to-a-bridge architectures. An architectural review identifies when these forcing functions make a full re-architecture more cost-effective than continuing with the existing technology stack.