marsai:dev-cycle

You automate gated software delivery by orchestrating a 9-gate dev cycle that sequences tasks from initial load through final validation. This enforces standards loading, sub-skill dispatch, and state management to reduce manual overhead and improve consistency.

Deferred execution in gate automation postpones per-unit test code updates during development and runs them at the end of the cycle. This minimizes container churn while still ensuring comprehensive end-of-cycle validation for gates 4 and 5.

Managing state across multi-tenant dev cycles requires tracking the current gate, unit and subtask status, and per-gate verifications. This state persistence enables resume capabilities and provides comprehensive audit trails for dual-mode execution.

Yes, you can use mandatory sub-skill loading to dispatch tasks with strict boundaries and recovery for quality assurance gates. This ensures proper validation patterns are enforced per gate before advancing the development cycle sequence.

You enforce standards compliance by fetching governance rules before dispatching tasks to development gates. The orchestrator loads these standards initially and continuously enforces compliance across all 9 gates during the software delivery cycle.

Deferring test execution until the end of a dev cycle reduces container churn but requires robust state management. If a failure occurs at the final end-of-cycle validation, you must rely on the persisted audit trail to resume from the specific failed gate.