executing-plans

Executing plans with batch checkpoints automates task processing by grouping dependent work together, running each batch sequentially, and pausing at checkpoints for verification and approval before proceeding to the next batch.

Constitution checks validate completed work against fail-fast principles and architectural patterns after each batch executes, flagging anti-patterns before they propagate and ensuring the implementation stays aligned with core design principles.

Yes, plan execution integrates Zen MCP to review and manage blockers across dependency groups, escalating issues before batch work begins so dependent tasks proceed only when prerequisites are clear.

Plans must be authored first using a plan-writing workflow that defines tasks and their dependencies; execution then reads the complete plan, maps dependency groups, and flags structural concerns before batch processing begins.

After each batch completes, checkpoint reporting presents verification results and completed work for architect review and approval, ensuring visibility and control before execution advances to the next dependency group.