iteration-closelisted

Close a product iteration the safe-but-ruthless way, in ANY repo — not tied to one product. Distill this iteration's decisions into the repo's own record, DELETE superseded baggage (git history is the archive — no _archive dirs, no .bak, no legacy- renames), verify two SEPARATE readiness channels (a confirmed cloud upload AND a tested zero-context takeover probe), rehearse the one-command new-machine bootstrap, then tag and seed the next iteration. Adapts to each repo's conventions and creates the minimum where one is missing. Run when an iteration or slice is done/approved and the user says any of — 收口 / 迭代收口 / 迭代收尾 / 收尾 / 收工 / 封版 / 发版 / 甩包袱 / 清旧账 / 蜕壳 / 这个迭代做完了 / 收尾上云 / close the iteration / wrap up this iteration / ship this iteration / finalize this iteration / done with this iteration. Also handles a STRUCTURAL overhaul as an in-repo iteration, never a new-repo restart. Product-agnostic; works in Claude Code and Codex.
m1nga/skill-builder · ★ 0 · AI & Automation · score 72

Install: claude install-skill m1nga/skill-builder

# iteration-close — distill, shed, prove takeover, rehearse bootstrap, seed next A product that iterates forever accumulates two silent debts, and this skill pays both down at every iteration boundary — safely (nothing is lost) but ruthlessly (nothing dead is kept): - Dead files linger and rot into two-truths — a deprecated tree sits around for weeks; a runbook keeps claiming a component is "not built" long after it shipped. - Knowledge that lives only in a chat window dies with it — a whole working pipeline once died in a scratchpad; hard-won decisions nearly died in chat. Keep the lesson, not the artifact. It is generic: it works on any repo by reading that repo's own conventions, and where a convention is absent it creates the minimum rather than assuming or erroring. "A fresh window or new machine can continue" is a HOPE until it is TESTED; being current (pull) is always safe, but publishing (push) is a deliberate choice. ## Step 0 — orient to THIS repo (discover, else plan to create) Read whichever entry doc exists — `CLAUDE.md` / `AGENTS.md` / `README` / a `docs/` index — and discover five things. Use what you find; where something is absent, note it as a gap this close will fill (each phase below says how), never invent a path that isn't there. 1. **Lesson/decision record** — where does this repo bank decisions? (`CHANGELOG`, `docs/adr/`, `DECISIONS.md`, or a repo-specific register.) If none, Phase 1 creates a single `DECISIONS.md`. 2. **Confirmed-upload co