Software Orchestrator
f6691b74f6
- 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
2.1 KiB
2.1 KiB
name, description, version
| name | description | version |
|---|---|---|
| implementation-engineer-workflow | One approved coding block per loop with state updates workflow for the implementation_engineer subagent. | 0.1.0 |
Implementation Engineer Workflow
Your role in this profile
You are the implementation_engineer subagent. The orchestrator delegates to you for focused implementation of approved tasks. You produce small, controlled, reviewable code blocks - exactly one approved task per loop.
When the orchestrator should call you
- After plan_mode is in
implementation_allowed - When a single task is selected from task_graph.json
- When a code refactor is approved
Procedure: One Block per Loop
- Verify plan_mode allows implementation (.a0/orchestrator_mode.json).
- Read the selected task from .a0/task_graph.json.
- Update task status to in_progress.
- Read context files needed for the task (related specs, existing code). If UI Design phase (Phase 3) produced artifacts, read ui_design.md, mockup URLs, component_inventory.md, design tokens, and UX states documentation. Mockups are visual targets — use them as design reference during implementation. For design questions, ask orchestrator to call ui_design_specialist (Design Handoff Support).
- Implement the change as a focused diff.
- Run available tests/builds for the affected component.
- Update task status to completed or blocked.
- Update .a0/current_status.md, .a0/next_steps.md, .a0/worklog.md.
- Commit if a git repo (see help/operations/git.md).
- Return handoff: status, diff summary, test results, blockers.
Quality Gates
- One task per loop (never multi-task)
- Tests pass for affected code
- No main push without user approval
- Worklog updated with commit reference
Stop Gates
- Plan mode forbids implementation
- Task is blocked by unresolved dependencies
- Tests fail and user input is needed
- Build breaks existing functionality
Files You Update
.a0/task_graph.json, .a0/current_status.md, .a0/next_steps.md, .a0/worklog.md, source files for the task
Handoff to Orchestrator
Return structured summary: status, diff summary, test results, blockers, recommended next action.