← ClaudeAtlas

leanforge-productization-releaselisted

Use when preparing, reviewing, or shipping a Leanforge productization or release batch, including GitHub releases, tags, About metadata, README quickstarts, CI, install/troubleshooting/migration docs, examples, support docs, PR hygiene, and post-merge validation. Use for Leanforge repository release checklists and recurring productization roadmap execution.
pkkgh1519/leanforge · ★ 0 · Code & Development · score 68
Install: claude install-skill pkkgh1519/leanforge
# Leanforge Productization Release Use this skill to ship Leanforge productization work without losing release hygiene. Keep it scoped to this repository unless the user explicitly asks to create a global skill. ## Operating stance - Prefer small PR batches over one broad productization PR. - Treat `main` as the release baseline. - Do not rewrite release history or move existing tags without explicit approval. - Use draft PRs by default, then mark ready only after review and passing checks. - Keep official docs neutral and product-grade; do not include persona, internal conversation context, or speculative claims. - Do not claim validation unless it ran. If blocked, state the exact blocker and strongest substitute evidence. ## Standard batch order 1. Release surface: - verify tags and GitHub Release; - update repository About description, homepage, and topics; - confirm release notes explain compatibility and validation. 2. First-run surface: - README badges; - install commands; - verify-install section; - first successful run path. 3. User support docs: - installation; - troubleshooting; - rename or migration guidance; - README links. 4. Examples: - workflow examples before generated sample apps; - copy-paste prompt bodies; - expected decision and evidence shape. 5. Operations docs: - contributing; - security policy; - support process. 6. Optional polish: - social preview; - screenshots; - richer demos. ##