run-plan

To execute a plan in an isolated git worktree, place a valid plan file in the docs/plans directory and run the execution command with the plan slug. The system applies changes in small blocks with micro-commits and runs a final validation gate before completion.

The best way to keep git history traceable during multi-step changes is using micro-commits per block. This approach applies plan changes sequentially in an isolated worktree, ensuring each modification is small, auditable, and gated by reviewers before final completion.

Yes, automating plan execution requires a Git repository containing a plans directory and a valid plan file. You also need a SKILL.md frontmatter to define the skill scope and prerequisites before triggering the isolated worktree workflow.

Yes, automated per-block reviewers can be assigned to evaluate changes as they are applied in the isolated worktree. These reviewers coordinate with a gate-driven final validation step to ensure all plan blocks meet quality standards before completion.

Triage integrates with plan execution by retrieving valid plans from the /triage output. Once retrieved, the plan is executed in a dedicated worktree where changes are applied in blocks, reviewed, and validated against governance gates before merging.

You should avoid using isolated worktrees for plan execution if your repository lacks a docs/plans directory or a valid plan file. Additionally, without a SKILL.md frontmatter to define prerequisites, the automated gating and micro-commit workflow cannot properly orchestrate the changes.