develop

What problem does it solve? Turning an approved design or architecture spec into working code often means re-deciding things that were already settled, inventing load bearing choices mid build, or losing track of progress across sessions. This Skill gates every build on a recorded spec, then implements the feature (UI, backend logic, or both) while tracking scope status so work is resumable and never silently diverges from the decision. ## Core Features & Use Cases - Spec gate before building: Checks that every value the build must produce has a named source in the spec; if a load bearing decision is missing, it routes to the architect flow or records an assumed spec instead of guessing. - Dual build tracks: A UI track covering design systems, tokens, semantic HTML, accessibility, and responsive states, plus a logical track covering data layers, migrations, APIs, authorization, idempotency, and integrations. - Scope and spec lifecycle management: Advances feature status in scope files, ticks build plan tasks, mirrors spec status transitions, and emits verify steps derived from acceptance criteria. - Use Case: A developer has an approved spec for an authentication feature. Run the develop command and it reads the spec and project conventions, builds the sign in pages plus session logic, applies the migration and confirms the schema is live, then updates the scope and offers verify steps. ## Quick Start Ask the agent to run /develop on a feature that already has an approved spec, for example: build the accounts sign in feature from its spec.