dev-cycle

You orchestrate a multi-gate development cycle by executing tasks through a six-gate pipeline spanning implementation, devops, SRE, testing, review, and validation. This enforces strict gate ordering and binary completion criteria for reliable feature delivery.

State persistence for interrupted workflows works by saving structured JSON state after each gate or task checkpoint. This allows the system to resume or retry development cycles exactly where they left off without losing prior progress.

Yes, you can load PM task files to drive TDD and code review workflows. The orchestrator reads these files to execute tasks sequentially through the gates, ensuring mandatory sub-skills are loaded before agent dispatch.

The best way to enforce quality standards during agent dispatch is by applying anti-rationalization checks and mandating WebFetch of Ring standards. This prevents the agent from skipping critical steps or bypassing required reviewers.

Yes, the development cycle orchestrator supports per-gate and per-task checkpoint execution. It provides multiple commit timing options to granularly control state persistence and workflow progression.

You need a structured gate pipeline for refactoring workflows to eliminate ad-hoc execution and enforcement gaps. It guarantees every subtask passes prescribed implementation, testing, SRE, and validation gates with persistent metrics.