launch-checklist
Create and execute comprehensive launch checklists so releases are coordinated, safe, and fully enabled across product, eng, marketing, sales, and support. Use when preparing any meaningful product or feature launch.
- License 许可
- MIT
- 最近更新
- 2026-07-22
- Stars
- ★ 7
- Forks
- 1
01 前言 Front Matter
- name
- launch-checklist
- description
- Create and execute comprehensive launch checklists so releases are coordinated, safe, and fully enabled across product, eng, marketing, sales, and support. Use when preparing any meaningful product or feature launch.
03 SKILL.md 正文
Launch Checklist
Overview
Launches fail more often from coordination gaps than from code bugs. A good checklist makes dependencies, owners, and readiness criteria explicit.
When to Use
- Feature or product launches
- Pricing or packaging changes
- Migrations or breaking changes
- Marketing-led moments tied to product capability
Typical Checklist Domains
- Product scope and success metrics
- Engineering readiness and feature flags
- QA / validation / performance
- Documentation and in-product guidance
- Support playbooks and macros
- Sales / CS enablement
- Marketing and comms
- Legal / compliance / security review
- Monitoring, alerts, and rollback plan
- Post-launch review schedule
Principles
- Assign a single owner per checklist item
- Distinguish launch-blocking items from nice-to-haves
- Run a readiness review before go-live
- Include explicit abort criteria
- Capture what to improve for the next launch
Verification
- [ ] Blocking items have owners and status
- [ ] Rollback / mitigation path exists
- [ ] Support and GTM teams are ready before traffic hits
04 同仓库更多 Skills
compliance-monitoring
Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.
complaints-handling
Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.
aml-kyc-basics
Apply AML/KYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.
ai-model-compliance
Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.
data-quality-management
Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.
data-lineage
Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.