task-execute

Provide a plan.md containing a PR-split table with dependency tracking. The Skill selects the next unstarted subplan whose dependencies are complete, creates a git worktree, delegates implementation to a background subagent, then runs a separate review subagent before reporting results.

The Skill does not proceed without plan.md. It instructs you to run the task-plan skill first, since planning and execution are separate responsibilities and task-execute only covers worktree creation through PR creation.

The reviewer subagent outputs findings with severity levels (Critical, Major, Minor) but no final verdict. The main agent decides: zero Critical and Major means PASS, small fixes become DIRECT_FIX, and two or more Critical findings trigger re-delegation to a fix subagent.

No. The Skill commits changes and generates a GO decision package, then reports to the user with a structured template. Only after explicit user OK does it run the PR size check, push the branch, and create the pull request.

Worktrees isolate each subplan's implementation in a separate working directory under .trees/ based on the latest origin/main or a specified base branch. This prevents interference with the main working tree and supports stacked subplans on dependency branches.

The precedent-pull step depends on an MCP tool that may not be running in all environments. If unavailable, the step is skipped and the GO package's pull.presented field remains 'unavailable', which biases decisions toward pre-GO human review.