next-tasklisted

# next-task — extend-op backlog-to-branch orchestrator `next-task` is an `extend` op-cell: select one real backlog item, isolate it, implement it, prove it, and end at an explicit delivery decision. It is a workflow driver, not a suggestion engine. It records the chosen task verbatim, separates planning from implementation, runs quality gates before publish, and never pushes until the final user decision. Load these local references before running the workflow: - `references/isolation.md` — detached-HEAD setup, branchless recovery, branch/push/PR path. - `references/gates.md` — slop, docs/changelog, review-loop, and repo-native verifier gates. ## When to Apply / NOT Apply when the user explicitly asks for the next task, backlog work, next issue selection, or a complete task-to-branch workflow. Do **not** apply for ad-hoc bug fixes with a known target, pure review, pure planning, broad project audits, speculative roadmap work, or any task that should stay in the current checkout. This skill is explicit-invocation-only. ## State Contract Use only `.outline/next-task/`: ```json { "flow.json": { "version": 1, "status": "selecting|isolating|exploring|planning|implementing|gating|complete|blocked", "phase": "source|selection|isolation|explore|plan|implement|gates|decision", "task": { "id": "", "source": "", "title": "", "body": "", "labels": [], "url": "" }, "policy": { "source": "", "filters": {}, "stopPoint": "publish|pr|local|queue|pick-another" },