Implement Task

Execute the tasks to-tasks published. The unit of dispatch is one ticket in one fresh context: its worker reads the ticket, design.md, and every task once, then works the tasks in number order as its checklist, one validation and one commit per task. execute.md is the whole procedure. The ticket footprint, the union of the projects its tasks name, is the only place the worker may write.

Given one task file, this skill runs execute.md itself for that task. Given a ticket or a feature directory, it orchestrates the frontier: independent ready tickets run concurrently in separate Git worktrees, each in a fresh sub-agent. The orchestrator owns merging, ticket acceptance, and the closing review.

1. Resolve the input

Accept one argument:

• A task file (<issues dir>/<NN>-<ticket-slug>/<MM>-<task-slug>.md) → single-task mode. Follow execute.md in direct mode for that task and stop when it reports.
• A ticket file or its task directory → orchestrate that ticket.
• A feature directory → orchestrate every ticket, in ticket dependency order.

Read the issue tracker convention (docs/agents/issue-tracker.md or whatever /setup-matt-pocock-skills configured) to locate tickets, task files, and the Status: vocabulary. Tickets whose tasks were not published by to-tasks (no Boundary section) are out of scope; say so and name $to-tasks.

2. Work the frontier

The frontier contains tickets not currently dispatched, whose blocking tickets are all done on the integration branch, and that still hold at least one task not done. A worker's report alone never clears a blocker: its branch must be merged and the ticket accepted first.