execute-plan

To execute an approved implementation plan safely, dispatch it through an autonomous agent loop that enforces workspace isolation and verification gates. This ensures code changes are carried out on isolated feature workspaces rather than main branches.

Workspace isolation prevents unsafe code execution by enforcing branch safety checks that restrict implementation to feature branches or worktrees. It strictly blocks execution on main or master branches, ensuring changes are validated before integration.

The best way to automate verification and review iterations is to force a formal verification phase after execution. This dispatches a controlled loop that automatically iterates on fix tasks discovered during the review of the implemented code changes.

Yes, you need an approved plan from create-plan before running agent-teams-driven-development. The execution Skill requires this plan path to dispatch implementation tasks and reviewers effectively within the isolated workspace.

No, you cannot run code execution directly on the main branch. CI safety checks explicitly prevent execution on main or master branches, requiring you to set up a feature branch or worktree before dispatching the implementation loop.

Your autonomous agent loop requires verification gates after implementation to ensure code changes are formally validated before completion. This controlled review and fix iteration loop catches task errors discovered during the verification phase.