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, and losing track of progress across sessions. This Skill gates every build on a recorded spec, then implements the feature (UI, backend logic, or both) following the project's own conventions, and updates the scope tracker when done. ## Core Features & Use Cases - Spec gate before building: Stops and routes to the architect step when a load bearing decision (auth provider, data model, page design) is unrecorded, or records it as an Assumed spec so the decision lives in the repo. - Dual build tracks: A UI track that enforces a professional design bar, design tokens, responsive layout, and WCAG accessibility, plus a logical track covering data layers, APIs, services, integrations, and migrations. - Scope and spec lifecycle tracking: Advances feature status in scope files, mirrors spec status from Proposed to Accepted, and emits verify steps tied to acceptance criteria. - Use Case: After running /architect to decide on a session based auth approach, run /develop to build the sign in pages and session logic, with the migration applied, tokens enforced, and the scope marked in progress. ## Quick Start Ask the agent to run /develop for a feature that already has an approved spec, for example build the accounts sign in feature from its spec.