do-task

Skill: do-task

Executes one card through the full cycle. Thin orchestrator: the card supplies the contract, the guidelines supply the rules, pr-flow supplies the PR mechanics, watch-pr supplies the review cycle. Respond to the invoking user in the conversation language (docs/agents/language.md; unset → their language); team-visible surfaces follow language: in docs/agents/tracker.md.

Load before acting: ${CLAUDE_PLUGIN_ROOT}/shared/workflow-context.md, ${CLAUDE_PLUGIN_ROOT}/shared/card-format.md, ${CLAUDE_PLUGIN_ROOT}/shared/pr-flow.md, ${CLAUDE_PLUGIN_ROOT}/shared/autonomy.md, and ${CLAUDE_PLUGIN_ROOT}/shared/guardrails.md — this skill writes code, commits and pushes; the loading contract applies in full.

Automode contract

Invoking /do-task authorizes the complete flow: pickup → implement → validate → PR → labels → /watch-pr → notification. No "may I proceed?" — ever. The escalation points listed at the bottom are the only stops, and each follows the park protocol (autonomy.md): persist, notify with the exact question + resume command, exit cleanly. A parked run is a successful run.

Step 0 — Resolve and parse

• Roles per workflow-context (config first, then detection/defaults — a role that would need a question in an unattended run falls to its default and is recorded in the trace).
• Argument: card path (tasks/TASK-007.md), bare id (resolved via INDEX/tracker), or tracker URL (URL pins the tracker). Empty argument → list the unblocked todo cards and stop — choosing what to work on is the human's call, not automode's.

Step 1 — Pickup (the lock)

1. Read the card. It must be todo/ready-for-agent, not parked, with every blocked_by target done/closed — any open blocker → park (this is the #1 fleet collision).
2. Re-verify state immediately before transitioning (card-format § Concurrency). Mode B mechanics spelled out: read the assignee field right before setting it — already claimed by anyone → stop, another agent owns it; only an empty assignee may be taken.
3. Transition todo → in-progress per the lifecycle table.
4. Resume case: card already in-progress with our branch existing (branch name = card id) → resume from the branch's state, never restart or duplicate. How to reconstruct progress: run the card's Test criteria — the test results are the checkpoint (green = that slice is done; red/missing = resume there). Dirty working tree → inspect the in-flight diff and finish or commit it first; never stash away or discard work. in-progress by someone else (different assignee/branch) → stop and say so — not our card.