02-low-level-design
Installation
SKILL.md
Low-Level Design Skill
Use When
- A component boundary and its requirements are approved and developers need deterministic implementation detail.
Do Not Use When
- Do not use to revisit system architecture silently or to generate code without approved behavioural contracts.
Required Inputs
| Artefact | Source or provider | Required? | Missing behaviour |
|---|---|---|---|
| Approved HLD, requirements and ADRs | Phase 02/03 artefacts | Required | Stop if component ownership or interface is unresolved. |
| Language, platform and coding constraints | Technology decisions and engineering standards | Required | Return technology-neutral contracts when the stack is undecided. |