| name | sdlc-design |
| description | Phase 4 of the SDLC, used ONLY for user-facing features. Use this to produce UI/UX design documentation and a persistent design system before implementation. Triggers when tasks.md exists and the spec marked a UI surface. Coordinates with the ui-ux-pro-max skill to generate design-system/MASTER.md and per-page specs. Skip entirely for CLI tools, libraries, or backend-only work. |
Phase 4 — Design (UI/UX, conditional)
Run only when spec.md flagged a user-facing surface. Otherwise the orchestrator skips you.
Preconditions
specs/<feature>/tasks.md exists.spec.md UI surface? = yes.
Process
- Hand off to ui-ux-pro-max with
--design-system --persist.
- Ensure outputs land in:
design-system/MASTER.md — tokens, components, accessibility, states (the source of truth),design-system/pages/<page>.md — per-screen overrides.
- Cross-check the design against
spec.md acceptance criteria — every user-facing
criterion must have a corresponding screen/flow.
- If implementation tasks need new sub-tasks (e.g. "build Button component"), append them
to
tasks.md and note the addition.
Exit
Update .sdlc/state.json (phase=design). Persist checkpoint. Say: "Design system ready. Next: /implement."
Примітка (UK)
Фаза дизайну запускається лише для інтерфейсних фіч. Вся робота делегується скілу
ui-ux-pro-max, а результат зберігається у design-system/MASTER.md як єдине джерело правди.
