| name | ml-llm-system-design |
| description | Use when the user wants an end-to-end architecture document for an ML or LLM service, including components, integrations, workloads, data flow, NFR, and degradation modes. |
ML / LLM System Design
Read:
../../../ML LLM Delivery Pipeline/02 System Design Doc Template.md
../../../ML LLM Delivery Pipeline/ML LLM Delivery Pipeline and Required Documents.md
Use this skill for the architectural document that connects business scope to
implementation shape.
Cover
- executive summary
- context and scope
- requirements summary
- decision summary and trade-offs
- workload and operating model
- architecture overview
- components and integrations
- data flow
- reliability and degradation
- operations summary
Guardrails
- Keep PRD-level business context short.
- Put final chosen details here; move disputed decisions to ADRs.
- Mention concrete failure and fallback paths for ML/LLM behavior.