What problem does it solve? Implementing a UI feature directly in an interactive session bloats the context window with file reads and edits, leaving little room for the rest of the conversation. This Skill keeps the calling session lean by acting as a thin orchestrator: it writes a compact implementation brief to disk and spawns fresh, disposable worker agents that do the actual file reading and code writing. ## Core Features & Use Cases - Plan-driven implementation: Picks up the latest /plan-ui output (or a task description), honors resolved decision memos, and refuses to start while decisions are still open. - Worker orchestration: Spawns one builder agent per logical file group, a sonnet presentation-layer pass for semantic markup and styling, and a read-only standards/test-gap check. - Scoped safety gates: Checks for collisions only against the plan's own files, runs a scoped TypeScript type gate before validation, and resolves worker-raised decision memos inline via AskUserQuestion. - Use Case: After planning a new settings panel with /plan-ui, run this Skill to have workers implement the components, refine accessibility semantics, verify types compile, and receive a report listing the unit and E2E tests still needed. ## Quick Start Ask the AI to implement the planned UI feature using the most recent plan, for example by saying "implement what we planned with impl-ui".
