dev-agent

To turn an idea into a build spec, you need an end-to-end workflow orchestration approach that guides you through design and prioritizes build output. This eliminates friction by applying a lean lifecycle navigation flow from idea to spec.

An execution-brief-first workflow uses a runtime status and next mechanism so you review only what is relevant for the current step. This prevents information overload by keeping project artifacts active in the workspace without reading entire documentation.

You manage role-based review by triggering specialist roles like reviewer, auditor, or test UI explicitly or when risk requires it. The dev agent applies these QA gates only during the optional release phases for fit.

Yes, you can skip phases because the workflow orchestration treats QA and ship as optional steps for fit. The agent chooses the right phase and runtime commands to progress iteratively within your existing workspace.

Yes, the dev agent requires using bin/dev-flow status and next to load the execution brief. These runtime commands ensure the agent reviews the correct current step and runs autonomy, delegate, or ui-polish when appropriate.

You should not use a lean end-to-end workflow if your project requires mandatory continuous QA gates rather than optional phases. This approach specifically prioritizes build output and applies release gates only when needed for fit.