feat: add ui_design_specialist (Phase 3 UI Design) v0.2.0

- New specialist: ui_design_specialist with iterative mockup dialog
- New Phase 3 (UI Design) between Architecture and Implementation
- Relay model: orchestrator passes responses verbatim in Phase 3
- Cost-control exception for UI Design phase (unlimited subagent calls)
- Webspace mockup workflow with cache-buster and obscure dirs
- UX states coverage (loading, empty, error, partial)
- WCAG 2.1 AA accessibility guidelines
- Design tokens (CSS custom properties) in design system
- Component states (hover, focus, active, disabled, loading, error)
- Sitemap/wireframe before mockups for complex UIs
- Real content strategy (no Lorem Ipsum)
- Form validation UX in mockups
- Dark mode and i18n support (optional)
- Design handoff support (specialist available during implementation)
- Skip mechanism for non-UI projects
- Mockup state file for context compression recovery
- Multi-page mockup strategy with index.html
- task_graph.json mockup references
- Plugin version: 0.1.14 -> 0.2.0
- 47 files changed across 7 implementation blocks
- 3 review rounds with 41 corrections integrated
This commit is contained in:
Software Orchestrator
2026-06-19 21:33:21 +02:00
parent 2343f0e717
commit f6691b74f6
44 changed files with 995 additions and 40 deletions
@@ -36,8 +36,9 @@ You are the requirements_analyst subagent. The orchestrator delegates to you for
3. Review architecture for alignment with requirements and library patterns.
4. Delegate to quality_reviewer to validate architecture, design, and task_graph.
5. Ensure tasks have clear dependencies and no circular references.
6. Update task_graph.json, .a0/current_status.md, .a0/next_steps.md.
7. Return handoff with plan status, quality review results, and open questions.
6. After architecture approval, the next phase is UI Design (Phase 3) — orchestrator delegates to ui_design_specialist. Implementation (Phase 4) follows after UI Design is approved.
7. Update task_graph.json, .a0/current_status.md, .a0/next_steps.md.
8. Return handoff with plan status, quality review results, and open questions.
## Quality Gates
- Requirements are testable, acceptance criteria concrete, assumptions explicit, non-goals documented, open questions tracked