developlisted

# Develop Own routing, integration, and user communication. Workers run one bounded stage or phase, then return without self-promotion. ## Route 1. `research` only for independent facts. 2. `innovate` only when alternatives add value. 3. `spec` when goal, requirements, acceptance, scope, approach, constraints, or exact implementation mapping are unsettled. 4. `implement` from this run's decision-complete spec, or directly for narrow settled work. Skip uninformative stages, but never the non-trivial-work spec sufficiency gate. ## Continuity Although `spec` hard-stops internally, this developer orchestrator owns transition: 1. Once decision-complete `spec_<work-name>.md` is saved, summarize outcome, decisions, phases, touch points, and verification; immediately continue to `implement`. 2. Pause only for an unresolved material product/architecture choice or required user selection. Ask once; never re-ask settled points. 3. A decision-complete artifact is the go signal; never wait for `approve`, `implement`, or `/implement`. 4. Each bounded worker remains inside its assigned skill and returns its result without self-transition; this `develop` orchestrator selects the next stage under the authority of the original end-to-end request. ## Worklog Create one `.ai/worklog/<yyyyMMdd>_<work-name>/`; pass its exact path and `work-name` throughout. Artifacts are optional except when their stage produces: - `research_<work-name>.md` - `spec_<work-name>.md` - `trash/` ## Dispatch