run-phase

Multi-phase development workflows are coordinated by orchestrating plan, execution, and review steps with persistent state. This approach dispatches specialized agents in parallel, enforcing safety checks and state persistence in a YAML file before phase completion.

Persistent state management for interrupted development workflows works by tracking progress in a .claude/dev-workflow-state.yml file. This mechanism maintains the current phase, step, and execution context, enabling work to resume after crashes or session interruptions.

The best way to structure a plan-execute-review cycle is by orchestrating it from scope confirmation to phase completion. This includes generating phase-specific plan artifacts, executing tasks via parallel agents, and performing mandatory verification, testing, and reviews.

Yes, you can use parallel agent dispatch to handle execution and validation tasks simultaneously. The workflow dispatches specialized agents, such as Opus for judgment, Sonnet for execution, and UI reviewers for design validation, concurrently within the same phase.

Yes, you need a development guide loaded to start a phase-based workflow. You begin by loading the dev-guide, confirming the first phase scope, and then initiating the plan-execute-review cycle for that specific phase.

You should not use stateful orchestration for development phases when your project lacks defined design docs or requires no multi-agent coordination. The approach enforces scope checks, UX alignment, and safety checks that may be excessive for simple, single-agent tasks.