Architecture Design

Turn a structural question into an implementable decision grounded in repository facts, ownership, quality attributes, and executable checks.

Use this skill

• Decide package, module, service, storage, protocol, deployment, ownership, public-contract, or multi-file structure.
• Write ADRs, architecture reports, decompositions, topology reviews, and migration plans for reliability, security, performance, evolvability, operability, or cost.
• Do not use for a local naming, formatting, or behavior-preserving edit with no structural effect.
• Redirect selected-topology enforcement to $architecture-enforce, policy ownership to $repo-governance, and agent-system or tool-routing prompt design to $prompt-engineering.

Rules

• Inspect callers, contracts, tests, build and deployment graphs, public surfaces, and repository guidance before deciding.
• State scope, stakeholders, constraints, owners, boundaries, public contracts, and measurable quality scenarios.
• Compare at least two materially different candidates and a do-less baseline for every nontrivial decision.
• Give every changed path one durable owner, responsibility, visibility, lifecycle, dependency direction, and reason it remains separate.
• Never hide warnings or failures with exclusions, threshold changes, ignores, disabled rules, or tolerated failed checks.