architect-design

# Architect Design Use this skill only as the manually selected `architect-design` stage. Its job is to extract the minimum required repository context first, then learn the required architecture knowledge, then produce one approved architecture design bundle that later `architect-propose` and `architect-build` work can execute without guessing. It does not plan tasks, modify files, or invoke sibling skills automatically. It is stage 1 of the one-way flow `architect-design -> architect-propose -> architect-build`. ## Defined Terms - `architect-design`: the manual `architect-design` stage that studies the codebase, learns the relevant architecture knowledge, asks for the compatibility boundary, and produces one approved design bundle. - `minimal context extraction`: the smallest repository-focused evidence pass required before any knowledge injection or design reasoning begins. It extracts only the facts needed to identify what the system is, where the requested change lands, what currently owns the behavior, which callers and tests matter, and which constraints already exist. - `basic repository understanding`: the post-extraction state in which the agent can state the system purpose, relevant entry points, affected modules, current behavior owner, caller path, state flow, constraints, and current tests for the requested change. This is a required gate, not a vague impression. - `design bundle`: the complete approved output of one `architect-design` ...