What problem does it solve? It keeps frontend feature work bounded and verifiable by requiring an approved SPEC and PLAN before any code changes, preventing scope creep, unauthorized contract changes, and unverified claims of completion. ## Core Features & Use Cases - Approved-task enforcement: Requires an exact approved SPEC and frontend PLAN, selecting only the first eligible task via the implement-next companion workflow. - Contract-safe implementation: Uses feature-local API modules, shared UI primitives, and narrow state scoping while keeping authorization decisions on the server. - Verification and handoff: Verifies user-observable behavior with typecheck, lint, and tests, then hands off substantial work to code review with recorded evidence. - Use Case: A developer has an approved PLAN for a new settings page. This Skill selects the first unchecked task, implements it against the existing API contract, runs the validation commands, and reports changed files and untested paths. ## Quick Start Ask the assistant to implement the first eligible task from the approved frontend PLAN for your feature, verifying behavior before claiming completion.
