architecture-workshop

To design architectural options for gaps in existing patterns, you need a framework that identifies constraints and generates both light-touch and architecture-shift approaches. This skill structures that evaluation by comparing blast radius, incremental adoption paths, and long-term maintainability to guide your decision.

A light-touch refactoring solution minimizes blast radius and complexity by adapting current design patterns, while an architecture shift proposes structural changes for better long-term fit. This skill evaluates tradeoffs like risk, complexity, and future reuse to recommend the appropriate approach for your codebase health.

You need to evaluate blast radius and incremental adoption paths for scalability when existing design patterns cannot accommodate new requirements. This skill applies a guided decision framework across modules to assess long-term impact and maintainability before committing to structural changes.

Yes, you can apply this architectural decision framework across multiple modules to evaluate pattern fit and propose structured recommendations. It enforces explicit criteria and maintainability considerations for each module, ensuring incremental adoption remains consistent throughout the codebase.

The best way to choose between refactoring approaches for design pattern gaps is to evaluate explicit criteria including risk, complexity, and future reuse. This skill generates structured recommendations by comparing light-touch versus architecture-shift options to prioritize long-term codebase maintainability.

Your current architecture may not fit new scalability requirements because existing design patterns lack the flexibility to handle increased complexity. This skill helps identify those constraints and generates alternative architectural options with explicit tradeoffs to address the gaps.