project-dev

You can orchestrate complex projects by coordinating sub-agents to execute multi-step plans autonomously using structured waves, quality gates, and rollback procedures. This enforces task ownership across brainstorm, plan, implement, and review cycles.

The best way to track overnight execution is using durable tracking files like PROGRESS.md, CONTEXT.md, and QA-REPORT.md. These files preserve state for recovery after interruptions and monitor status during autonomous sub-agent execution.

Yes, you can run feature development phases while AFK by initiating an overnight workflow. This uses concurrent sub-agents with gate-driven ship processes and cross-model review requirements to ensure reliable delivery without active monitoring.

The quality gate process works by enforcing structured waves and completion criteria during multi-phase migrations. Cross-model reviews and rollback procedures are required before advancing, ensuring reliable autonomous delivery and verifiable quality.

No specific dependencies are required to coordinate long-running initiatives. The workflow operates autonomously using built-in scripts and reference components to manage durable state tracking and sub-agent orchestration.

You should avoid sub-agent orchestration for simple, single-step tasks that do not require durable state tracking, multi-phase planning, or autonomous overnight execution, as the structured waves and quality gates add overhead for minor workflows.