feature-startlisted

# feature-start Prepare a clean, well-contextualized starting point for implementing one task, then stop for a plan approval gate. ## Steps 1. **Pick the task.** Confirm the task's **identifier and slug** with the user. The identifier is the GitHub issue number by default; on another tracker its key (`ENG-123`); in **local-only** mode the `#` column of the task table in `docs/progress.md`. Never invent one. One task per run. 2. **Isolate the workspace — default to a feature branch.** Create `feat/{id}-{slug}` directly. Only reach for an isolated **git worktree** (delegating to `using-git-worktrees` if installed) when isolation is genuinely critical — parallel work on multiple features, or disposable experiments — or when the user asks. Either way, FIRST run these guards (the worktree skill does them for you; the branch path must not skip them): - **Clean tree:** `git status --porcelain` is empty — nothing uncommitted to clobber. If the *only* change is the local-only tracker (`docs/progress.md`) that Decompose just wrote, ask to commit it and continue once approved — this is the gate that clears it. If the default branch is PR-protected, a direct commit there can never be pushed: land it via a `plan/{NNNN}-{slug}` branch → PR → merge first, same as any other planning commit (`AGENTS.md` → Where planning commits land), then branch `feat/*` from the updated default branch. Anything else: stop. - **Fresh base:** check out the d