next-task
Next Task
If a task ID is supplied, target that exact task; otherwise pick the highest-priority unblocked task from TASKS.md and work on it autonomously. Queue mode loops until the queue is empty or the user stops you; targeted mode stops after that task is shipped or explained.
Ship-it mode
At the start of every invocation, check the current conversation for active /ship-it mode. If the user invoked /ship-it earlier in this session and has not explicitly disabled it, /next-task inherits that standing approval for the current repository or approved repo family.
When ship-it mode is active:
- keep all
/next-taskpicking, claiming, planning, blocker, and forbidden-work rules intact; - after task implementation, run the delivery path defined by
/ship-itfor the current repo: verification, explicit-file staging, commit, feature-branch push, PR create/update, CI watch/fix, merge when checks and repo rules allow, canonical branch reconciliation, documented mirror/release steps, safe worktree cleanup, and tooling-repo latest-recommended-updates refresh; - do not stop at "committed", "pushed", or "PR opened" unless a hard blocker remains;
- in queue mode, continue to the next task after each shipped task until the queue is empty or the user stops you; in targeted mode, stop after the requested task is shipped or blocked;
- do not treat ship-it mode as approval for actions
/ship-itstill forbids: public comments/reviews/messages, protected-branch direct pushes, unsafe force pushes, package publishes outside an allowed own-tool release path, or work owned by another human/agent.
If ship-it mode is inactive, keep the default /next-task behavior: commit the task, push the feature branch, open or update the PR, then stop only where this command says to stop.