01-high-level-design
Installation
SKILL.md
High-Level Design Skill
Use When
- Requirements are stable enough to choose system boundaries, responsibilities and cross-component flows.
Do Not Use When
- Do not use to invent missing requirements or specify classes, methods and algorithms.
Required Inputs
| Artefact | Source or provider | Required? | Missing behaviour |
|---|---|---|---|
| Approved SRS/PRD and constraints | Phase 01/02 artefacts | Required | Stop on unresolved architecture-driving requirements. |
| Current context, integrations and quality targets | Project context and owners | Required | Qualify unknown interfaces and create ADR questions. |