Executes plan files task by task through delegated build contexts with per-task commits.
npx skills add https://github.com/blauwtje/exo --skill implementing-blauwtje
Please help me install this Agent Skill. Skill: implementing Source: https://github.com/blauwtje/exo/tree/main/skills/implementing Command: npx skills add https://github.com/blauwtje/exo --skill implementing-blauwtje
Plan-task: commit trailers so a cleared context can resume. - Delegated builds and waves: Dispatches builds to an implementer agent with per-task budgets, running independent tasks in parallel git worktrees and cherry-picking green commits in plan order. - Drift and failure repair: Routes plan drift to a repair delegate, failed runs to a bug fixer, and ends with a branch review whose findings are fixed before shipping. - Use Case: After a planning session produces docs/plans/add-auth.md, invoke the Skill on that plan; it resolves the workspace, builds each task in a delegate, commits each green task, runs final verification, and hands off a reviewed branch. ## Quick Start Ask the AI to run the plan at docs/plans/add-auth.md using the implementing skill and commit each task as it goes green.High-intent search queries and answers about installing and using this skill.
Invoke the implementing skill with the plan path, for example /exo:implementing docs/plans/add-auth.md. It reads only the plan's frame, lists tasks with grep, and dispatches each task's build to a delegate, committing each green task with a Plan-task trailer.
Resume by invoking the skill on the same plan; it never trusts memory. The next-task script inspects branch commits for Plan-task trailers to determine what landed, then picks the first ready task whose dependencies all landed.
Yes, when the plan carries a Worktree setup line, holds four or more tasks, and the current task has no Design line, the skill forms a wave of at most two tasks. Each builds in its own git worktree and commits are cherry-picked in plan order once every report is green.
The next-task script prints a PLAN DRIFT line when a Modify region is missing, duplicated, or already changed, stopping that task before any edit. A drift-repairer delegate on opus rewrites only that task's section against the current tree, then the task is retried.
Do not use it for authoring or repairing a plan, which the planning skill owns, or for a decided change with no plan file, which implementing-batch handles. A failure whose cause is unproven goes to the debug skill instead.
The pick-reviewer script measures the diff against the merge base with git shortstat. Branches of at most five changed files and 200 changed lines go to the branch-reviewer agent; anything larger goes to branch-reviewer-deep at high effort.
aleksandrovDocument structured implementation plans with tasks, files, tests, and commit history.
GenEducationPrepare feature branches for release with tests, versioning, and pull requests.
agentic-inDiagnose software failures by reproducing, isolating, and validating root-cause hypotheses.
aslaiiExecute trivial tasks directly without spawning subagents or creating PLAN.md files.