launch-checklist
starsforks
How to install launch-checklist?
tranhieutt/software_development_department/launch-checklist
$npx -y skills add tranhieutt/software_development_department --skill launch-checklistGenerates a comprehensive software launch checklist covering technical readiness, customer communications, support, and go-live steps. Use when preparing for a product launch or when the user mentions launch checklist or go-live readiness.
SKILL.md
| 1 | When this skill is invoked: |
| 2 | |
| 3 | > **Explicit invocation only**: This skill should only run when the user explicitly requests it with `/launch-checklist`. Do not auto-invoke based on context matching. |
| 4 | |
| 5 | 1. **Read the argument** for the launch date or `dry-run` mode. Dry-run mode |
| 6 | generates the checklist without creating sign-off entries. |
| 7 | |
| 8 | 2. **Gather project context**: |
| 9 | - Read `CLAUDE.md` for tech stack, release surfaces, and team structure |
| 10 | - Read the latest milestone in `production/milestones/` |
| 11 | - Read any existing release checklist in `production/releases/` |
| 12 | - Read any launch, support, or communications notes in `docs/launch/`, |
| 13 | `docs/runbooks/`, or `production/releases/` if they exist |
| 14 | |
| 15 | 3. **Scan codebase health**: |
| 16 | - Count `TODO`, `FIXME`, `HACK` comments and their locations |
| 17 | - Check for any `console.log`, `print()`, or debug output left in production code |
| 18 | - Check for placeholder assets or copy (search for `placeholder`, `temp_`, `WIP_`) |
| 19 | - Check for hardcoded test/dev values (localhost, test credentials, debug flags) |
| 20 | |
| 21 | 4. **Generate the launch checklist**: |
| 22 | |
| 23 | ```markdown |
| 24 | # Launch Checklist: [Product Title] |
| 25 | Target Launch: [Date or DRY RUN] |
| 26 | Generated: [Date] |
| 27 | |
| 28 | --- |
| 29 | |
| 30 | ## 1. Code Readiness |
| 31 | |
| 32 | ### Build Health |
| 33 | - [ ] Clean build or release artifact generated for all target surfaces |
| 34 | - [ ] Zero release-blocking compiler or linter errors |
| 35 | - [ ] All unit tests passing |
| 36 | - [ ] All integration tests passing |
| 37 | - [ ] End-to-end or smoke tests passing for critical user journeys |
| 38 | - [ ] Schema migrations tested with rollback or recovery plan |
| 39 | - [ ] Release version correctly set and tagged in source control |
| 40 | - [ ] Performance and reliability benchmarks within agreed targets |
| 41 | |
| 42 | ### Code Quality |
| 43 | - [ ] TODO count: [N] (zero required for launch, or documented exceptions) |
| 44 | - [ ] FIXME count: [N] (zero required) |
| 45 | - [ ] HACK count: [N] (each must have documented justification) |
| 46 | - [ ] No unintended debug output in production code |
| 47 | - [ ] No hardcoded dev/test values |
| 48 | - [ ] All feature flags reviewed for launch defaults |
| 49 | - [ ] Error handling covers all critical paths |
| 50 | - [ ] Crash reporting and structured logging integrated and verified |
| 51 | - [ ] Dependency vulnerabilities triaged and accepted risk documented |
| 52 | |
| 53 | ### Security and Privacy |
| 54 | - [ ] No exposed API keys or credentials in source or build artifacts |
| 55 | - [ ] Authentication, authorization, and input validation verified on public endpoints |
| 56 | - [ ] Network communication secured (TLS, signed webhooks, secret rotation as applicable) |
| 57 | - [ ] Abuse protection, rate limiting, or bot controls enabled where required |
| 58 | - [ ] Privacy policy and data handling compliance verified |
| 59 | - [ ] Backup and restore path validated for stateful systems |
| 60 | |
| 61 | --- |
| 62 | |
| 63 | ## 2. Product Readiness |
| 64 | |
| 65 | ### Functional Scope |
| 66 | - [ ] All launch-scope features implemented or explicitly deferred |
| 67 | - [ ] Critical user journeys tested end-to-end |
| 68 | - [ ] Admin, support, and internal operational workflows verified |
| 69 | - [ ] Billing, notifications, integrations, and webhooks tested if applicable |
| 70 | - [ ] Data import/export, retention, or deletion flows verified if applicable |
| 71 | - [ ] Release notes and known issues drafted |
| 72 | |
| 73 | ### UX, Content, and Localization |
| 74 | - [ ] All placeholder copy and visuals replaced |
| 75 | - [ ] All user-facing text proofread |
| 76 | - [ ] No hardcoded strings (all externalized for localization) |
| 77 | - [ ] All supported languages translated and verified |
| 78 | - [ ] Text fits UI in all supported languages |
| 79 | - [ ] Help content, onboarding, and empty states reviewed |
| 80 | - [ ] Customer-facing documentation links are current |
| 81 | |
| 82 | --- |
| 83 | |
| 84 | ## 3. Quality Assurance |
| 85 | |
| 86 | ### Testing |
| 87 | - [ ] Full regression test suite passed |
| 88 | - [ ] Zero Sev1 (Critical) bugs open |
| 89 | - [ ] Zero Sev2 (High/Major) bugs open, or documented exceptions with owner approval |
| 90 | - [ ] Smoke test passed in staging or release candidate environment |
| 91 | - [ ] User acceptance or stakeholder sign-off captured |
| 92 | - [ ] Edge cases tested (no network, expired session, low storage, rate limits, retries) |
| 93 | - [ ] Backup/restore or disaster recovery drill completed if applicable |
| 94 | |
| 95 | ### Accessibility and Compliance |
| 96 | - [ ] Accessibility basics covered for target surfaces |
| 97 | - [ ] Consent, privacy, and legal notices reviewed |
| 98 | - [ ] Audit logging or regulated workflow checks verified if required |
| 99 | - [ ] App store or platform policy requirements met, if applicable |
| 100 | |
| 101 | ### Performance and Reliability |
| 102 | - [ ] Response time or startup time within budget |
| 103 | - [ ] Memory and CPU usage within budget |
| 104 | - [ ] Queue lag, background jobs, and async workflows within |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
