Release Planning
When to activate
2–4 weeks before a planned product release. You have a finalized feature list, team capacity, and a target launch date. Activation requires feature specs, engineering estimates, customer communication needs, and rollout strategy (phased vs. all-at-once).
When NOT to use
Not for real-time incident response or hotfixes. Not without clear scope definition (use this when scope is locked). Not for ongoing product iteration (this is for discrete releases). Not for managing day-to-day engineering tasks. Not without customer communication planning.
Release Planning Framework
Core Components:
- Scope lock: List of features, fixes, improvements included
- Timeline: Development, testing, approval, deployment windows
- Dependencies: Features blocking other features, infrastructure readiness
- Testing strategy: QA, user acceptance testing, staging validation
- Rollout plan: Phased, canary, all-at-once, or feature flags
- Communication: Customer communication, support prep, marketing alignment
- Risk mitigation: Known risks, mitigation steps, rollback plan
Go/No-Go Checklist:
- Engineering: All features complete and tested
- Product: All requirements met, customer feedback positive
- QA: All critical bugs resolved, P1 blockers cleared
- Support/CS: Documentation ready, team trained
- Marketing/Sales: Launch messaging ready, customer comms scheduled
- Infrastructure: Deployment infrastructure validated, rollback tested
- Executive: Business approval, customer success sign-off
Planning Checklist
- Define scope — List features, fixes, improvements; confirm this is everything
- Estimate effort — Get engineering time estimates per feature; flag dependencies
- Identify critical path — Which features block others? Sequence accordingly
- Map timeline — Dev complete date, QA window, staging validation, deployment window
- Define success metrics — What indicates successful release? (uptime, adoption, performance)
- Plan communication — When/how do customers learn about this? Beta? Announcement? Docs update?
- Document rollback plan — If something breaks, how do we revert?
- Identify risks — What could go wrong? Dependencies on external systems? Scaling risks?
- Plan testing strategy — QA coverage, user acceptance testing, performance testing
- Create approval gates — Who signs off at each stage? What's required for sign-off?
Output Format
# Release Plan: [Release Name / Version]
**Target Launch Date:** [Date]
**Release Manager:** [Name]
**Status:** [In Planning / In Development / In QA / Ready to Deploy]
---
## Scope Summary
**New Features:**
- [Feature 1] — [Brief description, engineering estimate]
- [Feature 2] — [Brief description, engineering estimate]
**Bug Fixes & Improvements:**
- [Fix 1] — [Brief description]
- [Improvement 1] — [Brief description]
**Total Scope:** [X features, Y fixes, Z improvements] · **Est. Effort:** [X engineer-weeks]
---
## Timeline
| Phase | Start Date | End Date | Owner | Status |
|---|---|---|---|---|
| Feature Development | [Date] | [Date] | Engineering | [IN PROGRESS / COMPLETE / BLOCKED] |
| Code Review & QA | [Date] | [Date] | Engineering + QA | [IN PROGRESS / COMPLETE / BLOCKED] |
| Staging Validation | [Date] | [Date] | QA + Product | [IN PROGRESS / COMPLETE / BLOCKED] |
| Documentation | [Date] | [Date] | Product + Tech Writer | [IN PROGRESS / COMPLETE / BLOCKED] |
| Customer Communication | [Date] | [Date] | Marketing + CS | [IN PROGRESS / COMPLETE / BLOCKED] |
| Final Approval Gate | [Date] | [Date] | Executive + Product Lead | [IN PROGRESS / PENDING / APPROVED] |
| Deployment | [Date] | [Date] | Engineering + DevOps | [SCHEDULED / IN PROGRESS / COMPLETE] |
**Critical Path:** [Which feature/phase is most time-sensitive?]
---
## Dependencies & Blocking Risks
| Dependency | Blocker? | Status | Mitigation |
|---|---|---|---|
| [Feature A depends on Feature B] | YES / NO | On track / At risk / Blocked | [Plan B if blocked] |
| [Infrastructure readiness] | YES / NO | Ready / In progress | [Fallback plan] |
| [Third-party API / service] | YES / NO | Validated / Pending | [Contingency] |
---
## Testing Strategy
**QA Coverage:**
- Functional testing: All new features + impacted existing features
- Regression testing: [Scope of regression tests]
- Performance testing: Load test on [X concurrent users], validate response times <[Xms]
- Mobile testing (if applicable): iOS + Android devices
- Accessibility testing (if applicable): WCAG 2.1 AA compliance
**User Acceptance Testing (UAT):**
- Beta customers: [List or count]
- Duration: [X days]
- Success criteria: [What indicates UAT passes?]
**Staging Validation:**
- Deployment to staging by [Date]
- Full environment testing [Date]
- Sign-off by Product + CS [Date]
---
## Rollout Strategy
**Type:** [Phased / Canary / All-at-once / Feature Flag]
### Phased Rollout (if applicable)
**Wave 1 (Day 0):** [X% of users / specific segment] — [Date/time]
**Wave 2 (Day X):** [X% of users / specific segment] — [Date/time]
**Wave 3 (Day X):** [100% of users] — [Date/time]
**Success criteria per wave:** [What % adoption/engagement signals "OK to proceed"?]
### Feature Flags (if applicable)
- Feature flag: [Enabled for X% / specific segment]
- Monitoring window: [X hours]
- Rollout pace: [Increase by X% every X hours]
---
## Communication Plan
**Internal (Team & Leadership):**
- Engineering + QA standup [Date, time]
- Stakeholder go/no-go meeting [Date, time]
- Post-launch retro [Date, time]
**Customer-Facing:**
- Email announcement to [segment]: [Date]
- In-app notification: [Date/time]
- Changelog entry: [Live date]
- Blog post (if major): [Published date]
- Support documentation updated: [Date]
**Support & CS Prep:**
- Training session for support team: [Date]
- FAQ / Known issues doc: [Link]
- Escalation plan for early issues: [Process]
---
## Deployment & Infrastructure
**Deployment Environment:** [AWS / GCP / Heroku / On-prem / Other]
**Database Migrations:** [If any; planned downtime?]
**CDN / Cache Invalidation:** [Strategy]
**Monitoring:** [Key metrics to watch post-deployment]
**Rollback Plan:** [How do we revert if critical issue emerges?]
---
## Go / No-Go Checklist
**24 Hours Before Deployment:**
- [ ] All feature development complete and code-reviewed
- [ ] QA: All P0 & P1 bugs resolved; P2 bugs triaged
- [ ] Staging validation passed; no critical issues
- [ ] Database migrations tested and reversible
- [ ] Documentation complete and reviewed
- [ ] Support team trained; FAQ/escalation plan ready
- [ ] Customer communication drafted and approved
- [ ] Rollback plan documented and tested
- [ ] Monitoring dashboards configured
- [ ] On-call support assigned for deployment window
- [ ] Product lead: Final feature sign-off
- [ ] Engineering lead: Technical readiness sign-off
- [ ] VP/Executive: Business approval to proceed
**Go/No-Go Decision:** [APPROVED TO DEPLOY / HOLD / BLOCKED BY: [reason]]
---
## Risk Mitigation
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Critical bug in new feature emerges post-launch] | [HIGH / MEDIUM / LOW] | [HIGH / MEDIUM / LOW] | [Test plan, feature flag to disable quickly] |
| [Database migration fails] | [MEDIUM] | [HIGH] | [Rollback tested, data backup taken] |
| [Performance degradation] | [MEDIUM] | [HIGH] | [Load test pre-launch, monitoring alarms] |
**Escalation Contact:** [Name, phone number for on-call during deployment]
---
## Success Metrics
**Technical:**
- Deployment time: <[X] minutes
- Zero data loss or corruption
- Uptime maintained >99.9%
**Adoption:**
- [Feature adoption rate]: Target [X]% of eligible users in first week
- [Feature engagement]: Target [X] uses per session
**Customer Sentiment:**
- Support ticket volume related to release: <[X] in first 48h
- Customer satisfaction score: >=[X]/10
---
## Post-Launch Checklist
- [ ] Monitor error logs & performance metrics for 48 hours
- [ ] Gather customer feedback & support tickets
- [ ] Triage any issues discovered; create follow-up bugs
- [ ] Publish launch report (metrics, learnings, next steps)
- [ ] Schedule retro meeting to capture lessons learned
- [ ] Plan follow-up features/improvements based on feedback
---
Example
Release Plan: Product Operations Stack v1.2
Target Launch Date: June 30, 2026
Release Manager: Alice (VP Product)
Status: In QA
Scope Summary
New Features:
- Stakeholder mapper skill — [5 engineer-weeks]
- Metrics analyzer dashboard — [3 engineer-weeks]
- RACI template generator — [2 engineer-weeks]
Bug Fixes:
- Fix roadmap prioritizer sorting issue
- Improve session-log performance
Total Scope: 3 features · 2 bug fixes · Est. Effort: 10 engineer-weeks
Timeline
| Phase |
Start |
End |
Owner |
Status |
| Feature Development |
Jun 3 |
Jun 17 |
Engineering |
COMPLETE |
| Code Review & QA |
Jun 18 |
Jun 24 |
Engineering + QA |
IN PROGRESS |
| Staging Validation |
Jun 25 |
Jun 28 |
QA + Product |
SCHEDULED |
| Documentation |
Jun 20 |
Jun 28 |
Tech Writer |
IN PROGRESS |
| Deployment |
Jun 30 |
Jun 30 |
DevOps |
SCHEDULED |
Go/No-Go Checklist
Status: 9/12 items complete
1---2name: release-planning3description: Structures release scope, timeline, dependencies, and rollout strategy. Identifies critical path, risk mitigation, and communication checkpoints. Returns release checklist, timeline, and go/no-go criteria.4allowed-tools: Read, Write5effort: high6metadata:7 source: https://skillmd.com/skills/uitbreidenos/release-planning8---910# Release Planning1112## When to activate13142–4 weeks before a planned product release. You have a finalized feature list, team capacity, and a target launch date. Activation requires feature specs, engineering estimates, customer communication needs, and rollout strategy (phased vs. all-at-once).1516## When NOT to use1718Not for real-time incident response or hotfixes. Not without clear scope definition (use this when scope is locked). Not for ongoing product iteration (this is for discrete releases). Not for managing day-to-day engineering tasks. Not without customer communication planning.1920## Release Planning Framework2122**Core Components:**231. **Scope lock:** List of features, fixes, improvements included242. **Timeline:** Development, testing, approval, deployment windows253. **Dependencies:** Features blocking other features, infrastructure readiness264. **Testing strategy:** QA, user acceptance testing, staging validation275. **Rollout plan:** Phased, canary, all-at-once, or feature flags286. **Communication:** Customer communication, support prep, marketing alignment297. **Risk mitigation:** Known risks, mitigation steps, rollback plan3031**Go/No-Go Checklist:**32- Engineering: All features complete and tested33- Product: All requirements met, customer feedback positive34- QA: All critical bugs resolved, P1 blockers cleared35- Support/CS: Documentation ready, team trained36- Marketing/Sales: Launch messaging ready, customer comms scheduled37- Infrastructure: Deployment infrastructure validated, rollback tested38- Executive: Business approval, customer success sign-off3940## Planning Checklist41421. **Define scope** — List features, fixes, improvements; confirm this is everything432. **Estimate effort** — Get engineering time estimates per feature; flag dependencies443. **Identify critical path** — Which features block others? Sequence accordingly454. **Map timeline** — Dev complete date, QA window, staging validation, deployment window465. **Define success metrics** — What indicates successful release? (uptime, adoption, performance)476. **Plan communication** — When/how do customers learn about this? Beta? Announcement? Docs update?487. **Document rollback plan** — If something breaks, how do we revert?498. **Identify risks** — What could go wrong? Dependencies on external systems? Scaling risks?509. **Plan testing strategy** — QA coverage, user acceptance testing, performance testing5110. **Create approval gates** — Who signs off at each stage? What's required for sign-off?5253## Output Format5455```markdown56# Release Plan: [Release Name / Version]5758**Target Launch Date:** [Date]59**Release Manager:** [Name]60**Status:** [In Planning / In Development / In QA / Ready to Deploy]6162---6364## Scope Summary6566**New Features:**67- [Feature 1] — [Brief description, engineering estimate]68- [Feature 2] — [Brief description, engineering estimate]6970**Bug Fixes & Improvements:**71- [Fix 1] — [Brief description]72- [Improvement 1] — [Brief description]7374**Total Scope:** [X features, Y fixes, Z improvements] · **Est. Effort:** [X engineer-weeks]7576---7778## Timeline7980| Phase | Start Date | End Date | Owner | Status |81|---|---|---|---|---|82| Feature Development | [Date] | [Date] | Engineering | [IN PROGRESS / COMPLETE / BLOCKED] |83| Code Review & QA | [Date] | [Date] | Engineering + QA | [IN PROGRESS / COMPLETE / BLOCKED] |84| Staging Validation | [Date] | [Date] | QA + Product | [IN PROGRESS / COMPLETE / BLOCKED] |85| Documentation | [Date] | [Date] | Product + Tech Writer | [IN PROGRESS / COMPLETE / BLOCKED] |86| Customer Communication | [Date] | [Date] | Marketing + CS | [IN PROGRESS / COMPLETE / BLOCKED] |87| Final Approval Gate | [Date] | [Date] | Executive + Product Lead | [IN PROGRESS / PENDING / APPROVED] |88| Deployment | [Date] | [Date] | Engineering + DevOps | [SCHEDULED / IN PROGRESS / COMPLETE] |8990**Critical Path:** [Which feature/phase is most time-sensitive?]9192---9394## Dependencies & Blocking Risks9596| Dependency | Blocker? | Status | Mitigation |97|---|---|---|---|98| [Feature A depends on Feature B] | YES / NO | On track / At risk / Blocked | [Plan B if blocked] |99| [Infrastructure readiness] | YES / NO | Ready / In progress | [Fallback plan] |100| [Third-party API / service] | YES / NO | Validated / Pending | [Contingency] |101102---103104## Testing Strategy105106**QA Coverage:**107- Functional testing: All new features + impacted existing features108- Regression testing: [Scope of regression tests]109- Performance testing: Load test on [X concurrent users], validate response times <[Xms]110- Mobile testing (if applicable): iOS + Android devices111- Accessibility testing (if applicable): WCAG 2.1 AA compliance112113**User Acceptance Testing (UAT):**114- Beta customers: [List or count]115- Duration: [X days]116- Success criteria: [What indicates UAT passes?]117118**Staging Validation:**119- Deployment to staging by [Date]120- Full environment testing [Date]121- Sign-off by Product + CS [Date]122123---124125## Rollout Strategy126127**Type:** [Phased / Canary / All-at-once / Feature Flag]128129### Phased Rollout (if applicable)130**Wave 1 (Day 0):** [X% of users / specific segment] — [Date/time]131**Wave 2 (Day X):** [X% of users / specific segment] — [Date/time]132**Wave 3 (Day X):** [100% of users] — [Date/time]133134**Success criteria per wave:** [What % adoption/engagement signals "OK to proceed"?]135136### Feature Flags (if applicable)137- Feature flag: [Enabled for X% / specific segment]138- Monitoring window: [X hours]139- Rollout pace: [Increase by X% every X hours]140141---142143## Communication Plan144145**Internal (Team & Leadership):**146- Engineering + QA standup [Date, time]147- Stakeholder go/no-go meeting [Date, time]148- Post-launch retro [Date, time]149150**Customer-Facing:**151- Email announcement to [segment]: [Date]152- In-app notification: [Date/time]153- Changelog entry: [Live date]154- Blog post (if major): [Published date]155- Support documentation updated: [Date]156157**Support & CS Prep:**158- Training session for support team: [Date]159- FAQ / Known issues doc: [Link]160- Escalation plan for early issues: [Process]161162---163164## Deployment & Infrastructure165166**Deployment Environment:** [AWS / GCP / Heroku / On-prem / Other]167**Database Migrations:** [If any; planned downtime?]168**CDN / Cache Invalidation:** [Strategy]169**Monitoring:** [Key metrics to watch post-deployment]170**Rollback Plan:** [How do we revert if critical issue emerges?]171172---173174## Go / No-Go Checklist175176**24 Hours Before Deployment:**177178- [ ] All feature development complete and code-reviewed179- [ ] QA: All P0 & P1 bugs resolved; P2 bugs triaged180- [ ] Staging validation passed; no critical issues181- [ ] Database migrations tested and reversible182- [ ] Documentation complete and reviewed183- [ ] Support team trained; FAQ/escalation plan ready184- [ ] Customer communication drafted and approved185- [ ] Rollback plan documented and tested186- [ ] Monitoring dashboards configured187- [ ] On-call support assigned for deployment window188- [ ] Product lead: Final feature sign-off189- [ ] Engineering lead: Technical readiness sign-off190- [ ] VP/Executive: Business approval to proceed191192**Go/No-Go Decision:** [APPROVED TO DEPLOY / HOLD / BLOCKED BY: [reason]]193194---195196## Risk Mitigation197198| Risk | Likelihood | Impact | Mitigation |199|---|---|---|---|200| [Critical bug in new feature emerges post-launch] | [HIGH / MEDIUM / LOW] | [HIGH / MEDIUM / LOW] | [Test plan, feature flag to disable quickly] |201| [Database migration fails] | [MEDIUM] | [HIGH] | [Rollback tested, data backup taken] |202| [Performance degradation] | [MEDIUM] | [HIGH] | [Load test pre-launch, monitoring alarms] |203204**Escalation Contact:** [Name, phone number for on-call during deployment]205206---207208## Success Metrics209210**Technical:**211- Deployment time: <[X] minutes212- Zero data loss or corruption213- Uptime maintained >99.9%214215**Adoption:**216- [Feature adoption rate]: Target [X]% of eligible users in first week217- [Feature engagement]: Target [X] uses per session218219**Customer Sentiment:**220- Support ticket volume related to release: <[X] in first 48h221- Customer satisfaction score: >=[X]/10222223---224225## Post-Launch Checklist226227- [ ] Monitor error logs & performance metrics for 48 hours228- [ ] Gather customer feedback & support tickets229- [ ] Triage any issues discovered; create follow-up bugs230- [ ] Publish launch report (metrics, learnings, next steps)231- [ ] Schedule retro meeting to capture lessons learned232- [ ] Plan follow-up features/improvements based on feedback233234---235```236237## Example238239# Release Plan: Product Operations Stack v1.2240241**Target Launch Date:** June 30, 2026242**Release Manager:** Alice (VP Product)243**Status:** In QA244245---246247## Scope Summary248249**New Features:**250- Stakeholder mapper skill — [5 engineer-weeks]251- Metrics analyzer dashboard — [3 engineer-weeks]252- RACI template generator — [2 engineer-weeks]253254**Bug Fixes:**255- Fix roadmap prioritizer sorting issue256- Improve session-log performance257258**Total Scope:** 3 features · 2 bug fixes · **Est. Effort:** 10 engineer-weeks259260---261262## Timeline263264| Phase | Start | End | Owner | Status |265|---|---|---|---|---|266| Feature Development | Jun 3 | Jun 17 | Engineering | COMPLETE |267| Code Review & QA | Jun 18 | Jun 24 | Engineering + QA | IN PROGRESS |268| Staging Validation | Jun 25 | Jun 28 | QA + Product | SCHEDULED |269| Documentation | Jun 20 | Jun 28 | Tech Writer | IN PROGRESS |270| Deployment | Jun 30 | Jun 30 | DevOps | SCHEDULED |271272---273274## Go/No-Go Checklist275276**Status:** 9/12 items complete277278- [x] Feature development complete279- [x] Code reviewed280- [ ] QA: All P0/P1 bugs resolved281- [x] Documentation draft complete282- [x] Support team trained283- [ ] Staging validation passed284- [x] Rollback plan documented285- [x] Monitoring configured286- [ ] Product lead sign-off (pending QA completion)287- [x] Engineering lead sign-off288- [ ] Executive approval (pending product sign-off)289290---