rig-sprintlisted

Plan or run a sprint of independent tickets (or ad-hoc tasks). Use 'plan <feature>' to decompose a feature into independent tickets (no integration branch — each lands on the trunk on its own). Pass ticket IDs (or task descriptions) to execute them in phased dependency order with cleanup between phases. With no args (or just 'plan'), previews the current sprint-ready queue without launching anything. Triggers on: 'sprint', 'plan sprint', 'plan this as a sprint', 'break this into tickets', 'run tickets', 'execute tickets', 'run these tickets', 'kick off tickets', 'start sprint'.
agent-rig/rig · ★ 0 · AI & Automation · score 69

Install: claude install-skill agent-rig/rig

# Sprint Orchestrator A sprint is a batch of *independent* work items that each land on the trunk on their own. Use this when the work decomposes into pieces that don't interleave (no shared runtime contract across siblings, no half-migrated state if you ship one without the others). If children do interleave, use an epic / integration-branch flow instead — same decomposition step, plus a shared branch the children stack on. ## Configuration Reads `.rig/config.json` (missing keys → defaults): | Key | Default | Used for | |---|---|---| | `tracker.provider` | `none` | `linear` \| `github` \| `none`. Selects the ticket backend, or ad-hoc mode. | | `tracker.team` | — | Linear team / GitHub org for list/create. | | `tracker.project` | — | Linear project for list/create. | | `tracker.ticketPrefix` | — | Recognize ticket IDs in `$ARGUMENTS`. | | `tracker.githubIntegration` | `false` | If true, GitHub drives PR/merge transitions; each `/rig-task` sets only the start-of-work In Progress. | | `vcs.baseRef` | `origin/main` | Base each ticket's branch is cut from. | | `vcs.branchConvention` | `{user}/{ticket}-{slug}` | New-branch template. | | `vcs.defaultBranch` | `main` | Trunk each PR targets. | | `vcs.protectedBranchMergeQueue` | `false` | If true, merge via `gh pr merge --auto` and never pass `--rebase`/`--squash`. | | `runtime.installCommand` / `packageManager` | `npm` | Install command inside a worktree. | | `test.command` | `npm test` | Test step in each per-ticket implementa