to-tickets · git:20261118.581e4cd · 2026-11-18 · sha256 2fe4d5114fe04325

to-tickets git:20261118.581e4cdA

Immutable. This exact content never changes and is served at /api/v1/blob/2fe4d5114fe04325.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dyi4y7r3cazm5fiy/2fe4d5114fe04325e99588feb4e97bbbace20f560901bd143bace82677e06f1f.json

Then /plugin install to-tickets@markdownregistry-dyi4y7r3cazm5fiy in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: to-tickets
description: Decomposes a readiness-passed specification into a Scrum Sprint Wave Board (docs/sprint/SPRINT.md), cross-machine handover doc, and codebase-grounded vertical tickets citing reusable shared UI/helpers, config/logging seams, performance budgets, and acceptance criteria. Use when slicing a multi-session feature.
---

# To Tickets (Codebase-Grounded Vertical Wave Slicing)

Slice a readiness-passed spec into `docs/sprint/SPRINT.md` ([resources/sprint-board-template.md](resources/sprint-board-template.md)) and vertical tickets `docs/sprint/tickets/<NN>-<slug>.md` ([resources/ticket-template.md](resources/ticket-template.md)).

## Decision tree

1. **Does the work fit cleanly in a single session without waves?**
   - **Yes** → Do not generate sprint paperwork; run `/implement` directly.
   - **No** → Proceed to step 2.
2. **Does `specs/<slug>.md` exist with `Readiness Verdict: READY FOR TICKETS` (or a clear confirmed PRD)?**
   - **No** → Stop. Resolve ambiguities via `/to-spec` or `ask_question` first.
   - **Yes** → Proceed to step 3.
3. **Is `CONTEXT.md` populated with real shared UI, helpers, config/logging seams, and verification commands?**
   - **No** → Run `/index-project` first so every ticket cites real `path:symbol` reusable assets.
   - **Yes** → Build coverage ledger, confirm the Wave DAG with the user via `ask_question`, write tickets, and validate with the black-box script.

## Slicing workflow

1. **Coverage Ledger**: Map every `REQ-###`, `INV-###`, `NFR-###`, `SEC-###`, and `ERR-###` to an owning ticket, public seam, and test. An `OPEN` row blocks board creation.
2. **Repo-Grounded Vertical Slices**:
   - Each ticket (`S` or `M`, ≤1 session) delivers one observable vertical outcome cutting through validation, auth, domain rules, UI states, persistence, config/logging, error mapping, and tests.
   - Cite exact **Reusable Assets (`path:symbol`)** and **Config/Logging/Performance gates** inside each ticket. Never split out `Harden later`, `Wire UI later`, or `MVP` tasks.
   - Mark genuinely inapplicable checklist gates `N/A — <reason>` rather than inventing filler.
3. **Acyclic Execution Waves**: Put pure prefactoring at `#01` (`Wave 1`) if needed; compute `Blocked by` strictly from real data/contract dependencies.
4. **Validate via Black-Box Script**:
   ```bash
   node .agents/skills/to-tickets/scripts/validate-board.mjs --help
   node .agents/skills/to-tickets/scripts/validate-board.mjs docs/sprint/SPRINT.md
   ```