Execute plan.md phases with per-task worktree isolation and sequential commits.
npx skills add https://github.com/SeoJaeWan/try-claude-code --skill runner-seojaewan
Please help me install this Agent Skill. Skill: runner Source: https://github.com/SeoJaeWan/try-claude-code/tree/main/plugin/develop/skills/runner Command: npx skills add https://github.com/SeoJaeWan/try-claude-code --skill runner-seojaewan
Deterministic multi-phase plan execution requires strict isolation, per-phase commits, and careful gating to keep the main branch stable while tasks progress.
Create a per-task worktree and execute the ordered phases in plans/{task-name}/plan.md, prompting for approval after each phase and at the final merge decision.
High-intent search queries and answers about installing and using this skill.
Multi-phase plan execution uses task-level git worktree isolation to run ordered phases from plan.md, committing sequentially while keeping HEAD on the base branch. Each phase requires user approval before proceeding to the next step.
Keep your base branch stable by executing tasks in isolated git worktrees and keeping HEAD on the base branch. Worktrees provide lifecycle isolation, and per-phase commits ensure progress is tracked without directly modifying the main branch.
Mandatory user approvals are added through dev-review gating and Stop gates after each sequential phase commit. The orchestration pauses execution, prompts for human review, and requires explicit final merge decisions before completing the task.
Yes, per-task worktree isolation assigns one worktree per task to ensure lifecycle isolation. This allows ordered phases in plan.md to execute independently, with artifacts stored in plans/ and reviews/ for auditability and reproducibility.
Multi-phase plan orchestration uses a strict commit contract to ensure auditable and repeatable results. Sequential phase commits, dev-review gating, and stored artifacts in plans/ and reviews/ directories guarantee deterministic execution and traceable outcomes.
Isolated worktrees for plan execution are not suitable for simple, single-step tasks that do not require phase-level commits or human approval gates. Overhead from worktree management and strict commit contracts outweighs benefits for rapid, non-sequential development workflows.
LarryHsiaoAutomate Jira-backed Git workflows for branch creation and GitLab merge requests.
v1truv1usCreate, list, and remove Git worktrees for parallel development.
ozbyLaunch multiple blueprints in parallel across isolated git worktrees.
2lab-aiConfigure an AI work-execution system with gate checks, commit/PR conventions, worktree isolation, and deployment runbook.
