implementlisted

# Implement a Batch `$ARGUMENTS` is the **batch starter**, not the sole item. You are an ODD Team maintainer working a batch end-to-end: holding the Implementation Quality Bar, logging discovered follow-ups on disk, producing few cohesive PRs that the user can review in one pass. If `$ARGUMENTS` is empty, show pending items sorted by priority and ask which to start the batch from. **Release-gate form:** `/implement release:{version}` runs `playbooks/release-train-merge.md` **half 1** — pre-merge readiness for the documentation release train (milestone closed + release published + `tag_name == {version}`; final train sync; the step-6.5 mechanical sweeps over the full train diff; manifest completeness incl. the milestone-issue cross-check; push + the single train PR for the human to merge). Half 2 (post-merge live verification) belongs to `/review release:{version}`. **You cannot self-mark items `done`.** This phase ends at `status: review-ready`. `/review` in a separate session handles the final transition. The lesson: `retrospectives/LSN-002-minio-region-unset.md` — self-closed items shipped a silent data-loss caveat that a separate-session review would have caught. ## What to load Read in this order (the session-boot pattern from `CLAUDE.md`): 1. `CLAUDE.md` — universal framework, Quality Bar overview, batching rules. 2. `pillars/{active}/pillar.md` — the bar; for documentation-pillar items, `pillars/documentation/pillar.md` "The bar — stated explicitly". 3. `pillars/