system-design

Advancedworkflow

Mission

Understand constraints → explore options → decide → document. Produces a decision-backed architecture.

When to Use

Use when designing a new system, service, agent architecture, data pipeline, or infrastructure component; evaluating architectural options; making build-vs-buy decisions; or establishing constraints and tradeoffs before coding begins.

Triggers: “design this system”, “architecture for”, “how should we structure”, “system design”, “greenfield”, “architectural decision”

Skills Invoked

• arch-system — full component and boundary design
• arch-security — threat modelling (STRIDE)
• arch-reliability — SLA/SLO and failure modes
• arch-scalability — load model and scaling strategy
• req-analysis — requirements clarity pass
• req-scope — boundary definition

Chain-To

• feature-implement — proceed to implementation
• policy-govern — governance review of architecture

Example

{
  "request": "Design a multi-tenant SaaS authentication service with SSO and MFA support"
}

Output: Component diagram, API contracts, security threat table, SLA model, scaling recommendation, ADR log, and a handoff note for feature-implement.

Companion Tools

Use graph-visualize with chain-graph or skill-graph to inspect the instruction chain and skill topology.