night-sprintlisted

Delivers a whole feature overnight through autonomous sessions run strictly one after another, all on ONE branch landing as ONE pull request. A conductor session writes no code - it sets the sprint up, then a deterministic runner launches each ticket, advances the chain, revives what dies and waits out spending limits, escalating only what needs judgement. Each implementer watches its own context window and hands its ticket to a fresh session before it fills. Gets or builds a ticket breakdown first (via a spec and a ticket-splitting skill), decides whether to review once at the end or at checkpoints, runs each review as a FIND step plus a FIX step with only the review lanes that diff actually earns, optionally runs a test session that boots the stack or runs evals, and makes the required CI checks at the pushed sha decide whether the sprint delivered. Use when the user says "night sprint", "sprint this feature", "build this overnight", "run this while I sleep", "ticket after ticket", or wants a feature taken
amit-mizrachi/claude-amit-mizrachi · ★ 0 · AI & Automation · score 73

Install: claude install-skill amit-mizrachi/claude-amit-mizrachi

# Night Sprint ## Overview One feature, delivered overnight by a **chain** of sessions: ticket 01 lands, hands off to ticket 02, and so on. **Exactly one session touches code at a time**, all in **one worktree on one branch**, so the sprint ends as **one PR** with no integration step. You are the **conductor**. You never write product code. You set the sprint up, launch the first ticket, arm the runner, and then handle only what a script cannot decide. **`watch.sh` is a runner, not just a watcher.** It advances the chain, revives dead sessions and waits out spending limits by itself, logging everything to `state/EVENTS.log`. It escalates a short list of exceptions to you. Silence from it means the sprint is running. **This is the sequential sibling of `orchestrating-parallel-delivery`.** That skill splits work across concurrent sessions to save wall-clock. This one deliberately does not: it is night time, nobody is waiting, and serial execution buys correctness - no frozen contracts, no disjoint-file rules, no merge conflicts, no tracker. If you catch yourself fanning out implementers, you are in the wrong skill. `references/rationale.md` holds the incident history behind every rule here. Read it when you are changing the skill, not when you are running a sprint. ## Prerequisites - check these before kickoff, not at 3am Only `next-prompt` ships in this plugin. The rest are named by ROLE; substitute whatever you use, and write the real names into `PLAN.md` at kickoff s