develop

Run /develop with the feature name once its spec exists. The skill reads the spec's requirements and build plan, checks project conventions in MEMORY.md, then implements the UI or logical track and updates the scope checkboxes when done.

The Step 0 gate stops the build and asks how to proceed: route to /architect to deliberate a spec first, build directly if no real decision is involved, or record an assumed spec that blocks the feature from being marked done until ratified.

Yes, the UI track detects the framework from config files and package.json, then adapts routing, styling library, dark mode strategy, and icon usage to whatever the project already has installed.

Yes, the logical track generates and runs migrations against the target database, then confirms the schema is live by querying the real tables before marking the data layer task complete.

On Lean, Medium, and Full workflow tiers, /develop never marks a feature done; separate /check verify and /test steps close it. Only the Vibe tier lets the build self-check and mark done, and an assumed spec blocks done on every tier.

Do not use it to make architecture decisions, write spec rationale, or restructure project memory files; those belong to /architect, /audit, and /sync. It also requires an existing project scaffold unless the task is the scaffold step itself.