What problem does it solve?
It helps teams make disciplined, reproducible architecture decisions when changes touch multiple modules, introduce a new abstraction, or modify a shared contract, ensuring alignment and traceability.
Core Features & Use Cases
- Frame before proposing: Before proposing a solution, restate the goal, constraints, and the non-goal.
- Surface ≥2 alternatives: For non-trivial decisions, present at least two viable options with a one-line trade-off each.
- Ripple-effect analysis: Assess blast radius including affected files, contracts, downstream consumers, reversibility, and migration needs.
- Grounding discipline: Cite external sources for architectural invariants and surface assumptions with verifiable evidence.
Quick Start
Use the architect skill to frame a design issue before proposing a solution, and surface two alternatives with trade-offs.