---
description: Refine a batch of tasks via structured Q&A — resolve a set (feature or selector), refine each in dependency-correct order, emit a batch report; --depth ready audits, corrects and promotes each task
role: planner
argument-hint: "--feature <id> | --tasks <selector> [--focus <mode>] [--description <text>] [--depth <standard|ready>] [--agent <inline|auto|name>] [--auto] [--keep-going] [--status <s>] [--json] [--worktree [<name>]]"
allowed-tools: ["Bash", "Read", "Skill", "AskUserQuestion"]
---

# Dev Refineall

Wraps the **sp:spur-dev** skill. Batch counterpart of `/sp:dev-refine` — same per-task refine
operation, applied to a resolved set (typically every task under a feature). Pass
`--depth ready` to force an implement-ready freeze on every task (does not L3-SKIP). Each task's
existing claims are audited against the current tree and corrected, and passing tasks are promoted
`backlog → todo`. Use it to re-audit a feature's filed or stale tasks as well as before handoff.

## Argument Flags

| Flag | Description | Default |
| --- | --- | --- |
| `--feature` `<id>` | Refine all tasks in a feature. | required (one of `--feature` / `--tasks`) |
| `--tasks` `<selector>` | Task selector to refine (alternative to `--feature`). | required (one of `--feature` / `--tasks`) |
| `--focus` `<mode>` | Gap-analysis focus: `all\|requirements\|background\|constraints\|acceptance\|quick`. | `all` |
| `--description` `<text>` | Operator framing injected into each task's Q&A/synthesis. | omitted |
| `--depth` `<standard\|ready>` | Spec depth bar (see flag glossary). | `standard` |
| `--agent` `<inline\|auto\|name>` | Who runs the model-bearing refinement. | omit |
| `--auto` | Skip objective HITL gates. | off |
| `--keep-going` | Continue past per-task failures. | off |
| `--status` `<s>` | Only refine tasks in these statuses (applied in-agent to the frozen set). | `backlog` + `todo` |
| `--json` | Emit structured JSON. | off |
| `--worktree` `[<name>]` | Run the batch in an isolated git worktree; FF-merge on success, retain on failure. Bare `--worktree` creates a fresh tree; `--worktree <name>` adopts an existing worktree by name/path/branch. | off |

For shared semantics, see the [flag glossary](../skills/spur-dev/references/flag-glossary.md).

## Usage

```
/sp:dev-refineall --feature <id> [shared refine flags…] [--depth <standard|ready>] [--agent <inline|auto|name>] [--worktree [<name>]]
/sp:dev-refineall --tasks <selector> [shared refine flags…] [--depth <standard|ready>] [--agent <inline|auto|name>] [--worktree [<name>]]
```

Flags: `--feature` (sugar for `feature:<id>`), `--tasks <selector>`, shared refine flags
(`--focus`, `--description`, `--depth`, `--agent`, `--auto`),
plus `--keep-going`,
`--status` (default `backlog` + `todo`),
`--json`, `--worktree` `[<name>]` (run the batch in an isolated git worktree — FF-merge onto the base ref on
full success, retain intact on any failure/halt/non-FF; bare form creates a fresh tree, `<name>`
form adopts an existing worktree by name/path/branch; see `execution-batch.md` § Worktree
isolation). Prefer `--auto` for batch
scale. Full procedure: `plugins/sp/skills/spur-dev/references/dev-operations.md` § refineall.
**`--worktree` corpus visibility.** While the batch runs in a worktree, corpus writes land in the
worktree copy; your main tree still shows pre-run statuses until the FF-merge on success. Expected,
not a bug.

**Depth:** default `standard` keeps the cheap L3 SKIP gate under `--auto`. Use
`--depth ready` when handing a feature to another implementer (frozen Design/Requirements/Plan),
or when the tasks' existing content is in doubt; thread `--depth` into each per-task refine. Ready
report rows add corrections count, status before → after, and failed checklist ids.

> **`--next` dropped** (feature H8, 2026-07-31). Batch-level chaining was a token bomb — each refine
> hop is an LLM call, and a large feature means N refine chains fanned out at once. For batch
> chaining, run `/sp:dev-refineall` first (this command, no `--next`), then
> `/sp:dev-runall --feature <id> --next` which chains each task's run → verify → wrap sequentially.
> **was: `--next` declared with a self-contradicting "avoid --next" warning.**

## Implementation

- Apply the [inline-default execution-surface contract](../skills/spur-dev/references/cross-cutting.md#inline-default-execution-surface).
- Apply the [shared startup contract](../skills/spur-dev/references/cross-cutting.md#shared-startup-contract-task-0814-r1r3r4r6r7r8) — bootstrap checklist, quick readiness before isolation, workflow inventory before YAML, comprehensive checks at owning boundaries (task 0814 R1/R3/R4/R7/R8).
- Batch orchestration: `Skill(skill="sp:spur-dev", args="refineall $ARGUMENTS")`
- Per-task refine (inner): `Skill(skill="sp:spur-dev", args="refine <wbs> $SHARED_FLAGS")`