← ClaudeAtlas

prep-major-releaselisted

Prepare Hot Sheet for a major release — refresh the README so it stays compelling and advertises the most important + newest features, and review the demo scenarios/screenshots, producing a capture-ready plan of which shots to add, recapture, or drop. Use before cutting a major release (or on demand when a lot has shipped).
brianwestphal/hotsheet · ★ 6 · Code & Development · score 74
Install: claude install-skill brianwestphal/hotsheet
Get Hot Sheet's **public-facing surface** ready for a major release. Two deliverables: 1. **A refreshed `README.md`** — accurate, compelling, and advertising the most important + most *interesting* recently-shipped features. 2. **A capture-ready demo-screenshot plan** — which of the `docs/demo-N.png` shots to keep, recapture, or add (and any `src/demo.ts` / `scripts/capture-demos.ts` changes needed to seed them). The maintainer captures the actual screenshots afterward, so end with a clear, reviewed plan — don't try to capture yourself. The README and the screenshots are the first thing a prospective user sees. A lot ships between major releases; this skill closes the gap between "what the product does now" and "what the front page says it does." **Ground yourself first.** Read `docs/ai/requirements-summary.md` (the Shipped / Partial / Design-only status of every feature) and `docs/ai/code-summary.md` before judging what's worth advertising — they're the synthesized source of truth for what currently exists. Skim the recent `CHANGELOG.md` entries and `git log --oneline <last-tag>..HEAD` for the headline changes since the last release. Honor `CLAUDE.md`: **American English**, the project's existing voice, and the doc-sync rules. --- ## Part A — README review + update The README lives at `README.md` (~570 lines). Its public sections: the hero + one-line pitch, **Why Hot Sheet?**, **Features**, **AI Integration** (Claude Code, Claude Channel, Announcer, Telemet