What problem does it solve? It prevents teams from designing changes from task descriptions alone, which leads to architectures that ignore the existing codebase, break shared consumers, or introduce unnecessary new patterns. ## Core Features & Use Cases - Business-flow-first reasoning: Positions every task inside the user's business flow (WHO → FLOW → FEATURE → CODE → TECHNICAL DESIGN) before proposing any technical change. - Evidence-based system mapping: Maps business steps to actual code with path:line citations, finds the closest existing pattern, and traces bugs to root causes across all layers. - Shared Architecture Protocol: For shared or system-level changes, identifies all consumers, ownership, invariants, and blast radius so sibling features do not regress. - Use Case: Before planning a change to a pricing calculation, run this skill to produce an approved architecture design with a feature map, API contract, acceptance criteria, and regression surface that the planner, builder, and reviewer all follow. ## Quick Start Ask the AI to design the architecture for your confirmed task, for example: "Design the architecture for the notification settings feature based on the confirmed business context."
