executing-plans

Executing a development plan requires loading the written plan, reviewing it for concerns, and tracking tasks through in_progress and completed statuses. This process enforces stepwise execution, critical feedback, and formal completion reporting with guardrails against blockers.

Managing checkpointed tasks requires loading a written plan, converting it into actionable steps, and applying verifications at each checkpoint. This ensures disciplined progress tracking, subagent coordination, and formal completion reporting with guardrails against blockers.

Yes, you can coordinate subagents to execute implementation plans in separate sessions. The workflow identifies and executes written plans, applying critical review, stepwise execution, and guardrails against blockers to ensure separate session task delivery.

Plan-driven development requires formal completion reporting to ensure disciplined execution, progress checks, and clear handoffs. Without it, the workflow cannot enforce verifications, track status updates, or apply guardrails against blockers during task delivery.

Reviewing a written implementation plan involves loading the plan, identifying concerns, and converting it into actionable tasks. This critical review phase ensures the plan is sound before stepwise execution, verifications, and status tracking begin.