What problem does it solve?
Turning requirements into a concrete system architecture often produces vague diagrams, hidden assumptions, and unjustified technology choices. This Skill enforces an evidence-backed workflow that produces a target design with explicit boundaries, contracts, estimates, failure behavior, and recorded tradeoffs before any implementation begins.
Core Features & Use Cases
- Estimate-Driven Design: Computes request rates, storage growth, and bottleneck thresholds from sourced assumptions before selecting components, rejecting speculative scale.
- Structured Architecture Artifacts: Produces domains, data models, API contracts, HLD, critical LLD, failure modes, and operations models in a single target-design document.
- Decision Governance: Compares at least two credible alternatives per consequential decision, records reopen triggers, and returns READY, REVISE, or BLOCKED verdicts.
- Use Case: Given an approved requirements baseline for a new ordering platform, generate a target design covering service boundaries, data ownership, failure handling, and rollout implications that an implementation planner can consume directly.
Quick Start
Ask the agent to build a target system design from your approved requirements document and constraints, writing the result to docs/architecture/target-design.md.