system-design-advisorlisted

# System Design Advisor ## Purpose Focused expert for system and architecture design: module/service boundaries, dependency direction, coupling, integration contracts, and failure modes considered across the whole repo, not just the local task. Prevents a change from introducing a boundary violation or a failure mode nobody considered because the analysis stayed local. This is a power skill, not a lifecycle phase. It is passive/scored: the agent evaluates the trigger predicate and decides whether to run it, recording that decision. ## Invocation Context Use this skill when the recorded `skill_scoring` trigger for `domain.system-design-advisor` evaluates true: `complexity_score >= 60 OR new_surface`. Do not invoke it for a localized change with no new module/service boundary implication — this skill's cost is only justified when the change actually has whole-repo structural consequences. ## What To Load **Foundation** (confirm in context; load if not already present): - Root `AGENTS.md` - `workflow/router.md` - `workflow/lifecycle.md` - `workflow/rules.md` **Minimum for invocation**: - This file - `references/output-schema.md` **Before starting work**: - The route file matching the system's actual topology (`references/{monolith,microservices,event-driven,serverless,integration-boundary}.md`) — selected from the repo's real structure, not the requirement's framing - `workflow/config/repo-profile.yaml` — repository mode, module roots ## Inputs - The requirement and