| name | go-to-market-checklist |
| description | Generate a pre-launch readiness checklist for feature releases. Use this skill when:
- A feature is nearing completion and you need a launch readiness checklist
- You want to ensure all pre-launch items are covered (docs, training, support, rollback)
- You are planning a phased rollout and need a structured go-to-market plan
|
Go-to-Market Checklist
Generate a comprehensive pre-launch readiness checklist covering documentation, training, support, communication, metrics, and rollback planning.
Workflow
- Read feature spec from your spec directory
- Identify GTM dimensions from spec (users, channels, metrics, risks)
- Generate checklist with status tracking
- Output — Print to conversation or write file
Checklist
Documentation
Training
Support Readiness
Communication
Metrics & Monitoring
Rollback Plan
Compliance
Output Format
# Go-to-Market Checklist — {Feature Name}
**Target Launch:** {date}
**Feature Spec:** {path}
**Status:** {Ready / Not Ready — N of M items complete}
{checklist sections above}
## Go/No-Go Summary
| Dimension | Status | Blocker? | Notes |
|-----------|--------|----------|-------|
| Documentation | Ready/Not Ready | Y/N | {detail} |
| Training | Ready/Not Ready | Y/N | |
| Support | Ready/Not Ready | Y/N | |
| Communication | Ready/Not Ready | Y/N | |
| Metrics | Ready/Not Ready | Y/N | |
| Rollback | Ready/Not Ready | Y/N | |
| Compliance | Ready/Not Ready | Y/N | |
**Decision:** GO / NO-GO
**Blockers to resolve:** {list if NO-GO}
Anti-Patterns
- Don't skip the rollback plan — every launch needs a reversal path
- Don't launch without baseline metrics — you can't measure impact without a before
- Don't treat compliance as optional — data privacy is non-negotiable
Quality Checklist
