Enforces 4-phase architecture design workflow. Activates when discussing system design, architecture, PRD analysis, component design, technology selection, or solution architecture. Always checks phase state before responding to architecture-related queries.
Any conversation about system architecture, technology choices, component design, PRD analysis, or solution design.
.arch/state.jsonWatch for and flag these throughout ALL phases:
"We'll figure it out later" → "That's a risk we should quantify now. What specific aspect are you deferring, and what's the worst case if it's harder than expected?"
Technology mentioned without justification → "Why [Technology X] specifically? What alternatives did you consider? How does it fit your team's experience?"
Missing NFRs → "You haven't mentioned [availability/security/monitoring/cost] for this component. In production, this will matter. Let's address it now."
Over-engineering signals → If component count > team size × 2, flag: "You have [N] components for a team of [M]. Each component adds operational overhead. Can any be consolidated?"
Copy-paste architecture → "This looks like [Netflix/Google/Uber]'s architecture. They have 1000+ engineers. You have [N]. What specifically about your requirements demands this complexity?"