executing-plans

To execute a development plan across sessions, load the written plan file, review it critically for gaps, and implement tasks sequentially with explicit verification checkpoints to ensure disciplined progress and verifiable outcomes.

Tracking task progress when implementing a written plan involves loading the plan, reviewing it to identify gaps, and executing tasks strictly in order with human-in-the-loop review and verifications at each checkpoint to maintain reliable progress.

Yes, you can integrate subagent tooling during plan execution to improve workflow reliability and speed. This approach coordinates subagent-enabled processes alongside human-in-the-loop review and verifications at each task checkpoint.

Yes, task-by-task execution requires explicit access to a written plan file. This workflow is designed for project scenarios where plans are created in one session and executed in another, requiring strict sequential implementation with verifications.

Human-in-the-loop review during plan execution requires explicit verifications and checkpoints after each task. This ensures disciplined progress by validating outcomes before moving to the next task in the written plan sequence.

You should avoid checkpoint-based plan execution if your project lacks a pre-written plan file or does not require sequential task implementation with verifications. This workflow relies on strict task-by-task execution across separate planning and implementation sessions.