What problem does it solve? Consequential architectural decisions in a solo software build are often made on optimism or incomplete information, and wrong calls surface late as rewrites. This Skill applies structured engineering judgment at the moments where a wrong decision is expensive to reverse. ## Core Features & Use Cases - Architecture Review: Evaluates a proposed approach against the project's tech-context, discovery brief, and backlog using four questions: platform fit, blast radius, debt created, and expandability. - Single Recommendation Output: Produces one clear call with reasoning, named risks, explicit debt, early warning signals, and hard-stop conditions — not a menu of options. - Pushback Handling: Updates the recommendation when new information arrives, holds the position against unsupported preference, and records the tradeoff when the solo decides differently. - Use Case: After establishing the tech stack and before a design sprint, invoke the review to check whether the planned design locks in assumptions that conflict with platform constraints or will force a rewrite in a later phase. ## Quick Start Invoke the principal engineer review on the proposed architecture in docs/tech-context.md before starting the design sprint.
