ceratops-task-execute-in-stages

Staged workflow execution coordinates multi-stage task management by diagnosing problems, applying local fixes, verifying, and closing safely. It enforces minimal invasive changes and rollback-safe verification, advancing only when justified to prevent regressions during bug fixes or feature rolls.

The best way to structure a staged workflow for complex bug fixes is to separate diagnosis, local fix implementation, verification, and closure into distinct steps. This risk-aware progression ensures each stage is justified and enables immediate re-evaluation if new issues appear.

A staged execution workflow handles operational runbooks safely by applying risk-aware progression and state containment. It builds on prior evidence, enforces rollback-safe verification at each stage, and reverts or re-evaluates when new issues appear to minimize invasive changes and rework.

You should use a staged task execution strategy instead of direct changes when handling substantial tasks like feature rolls or operational runbooks. It is required when structured problem-solving demands risk-aware progression, minimal invasive changes, and rollback-safe verification to avoid regressions.

Yes, you can revert changes if stage verification fails during multi-stage task execution. The risk-aware progression model enforces rollback-safe verification and automatically reverts or re-evaluates the current stage when new issues appear, ensuring safe containment.