Production Readiness Generator
Goal
Create a comprehensive pre-launch checklist that outlines all user stories, acceptance criteria, and smoke tests that must pass before deploying to production.
Input Sources
- PRD File - Generate from
docs/prds/[n]-prd-*.md
- Feature Description - Generate from verbal description
- Existing User Stories - Extract from project documentation
Output
- Format: Markdown (
.md)
- Location:
docs/testplans/
- Filename:
production-readiness-[feature-name].md
Process
Phase 1: Context Gathering
Identify Input Source
- Check if user provided PRD, feature description, or reference to existing docs
- If PRD: read and analyze user stories and acceptance criteria
- If description: extract key functionality
- If existing: scan docs for user story patterns
GATE: Production Environment Confirmation
Ask the user:
This checklist is for PRODUCTION deployment validation.
Please confirm:
1. What is the current production environment? (URL, platform)
2. When is the planned go-live date?
3. Who is responsible for production deployment?
4. What is the rollback procedure if issues are found?
Do NOT proceed without explicit confirmation.
Gather Production Context
Additional production context needed:
1. What is the user impact of this feature? (all users, subset, opt-in)
2. Are there any compliance requirements? (GDPR, HIPAA, SOC2, etc.)
3. What are the SLAs/performance requirements?
4. What monitoring/alerting is in place?
Phase 2: User Story Extraction
Map All User Stories
Extract or generate complete set of user stories:
From PRD/Documentation:
- Scan for "As a [user], I want [action], so that [benefit]" patterns
- Extract acceptance criteria from requirements sections
- Identify edge cases and error scenarios
Generate if needed:
- Primary user flows (happy path)
- Edge cases and error handling
- Performance and scale scenarios
- Security and compliance scenarios
- Rollback and recovery scenarios
Categorize User Stories
Group by:
- Critical - Must work for launch (blocking)
- Important - Should work for launch (high priority)
- Nice-to-have - Can work after launch (non-blocking)
Phase 3: Generate Acceptance Criteria
Define Acceptance Criteria for Each Story
For each user story, create specific, testable criteria:
### User Story: [Title]
**As a** [user type]
**I want** [action]
**So that** [benefit]
**Priority:** Critical | Important | Nice-to-have
**Acceptance Criteria:**
- [ ] [Specific, measurable criterion 1]
- [ ] [Specific, measurable criterion 2]
- [ ] [Error handling criterion]
- [ ] [Performance criterion]
**Test Steps:**
1. [Step 1]
2. [Step 2]
3. [Expected outcome]
**Dependencies:**
- [Service, API, or feature this depends on]
Add Production-Specific Criteria
For each story, add:
- Performance: Response times, load handling
- Security: Authentication, authorization, data protection
- Monitoring: What metrics/logs to check
- Rollback: How to undo if this fails
Phase 4: Generate Production Smoke Tests
Create Smoke Test Checklist
## Production Smoke Tests
Run these tests IMMEDIATELY after deployment:
### 1. Core Functionality
- [ ] [Critical path 1]: [Expected outcome]
- [ ] [Critical path 2]: [Expected outcome]
### 2. Authentication & Authorization
- [ ] Login works for all user types
- [ ] Permissions are enforced correctly
- [ ] Session management working
### 3. Data Integrity
- [ ] Data reads correctly from production DB
- [ ] Data writes successfully
- [ ] No data corruption or loss
### 4. Integrations
- [ ] External API calls succeed
- [ ] Webhook deliveries working
- [ ] Third-party services responding
### 5. Performance
- [ ] Page load times < [X]ms
- [ ] API response times < [Y]ms
- [ ] No memory leaks or resource exhaustion
### 6. Monitoring & Alerting
- [ ] Metrics being collected
- [ ] Logs flowing correctly
- [ ] Alerts configured and firing appropriately
Phase 5: Generate Rollback Plan
Document Rollback Procedures
## Rollback Plan
If critical issues are found during validation:
### Rollback Decision Criteria
- [ ] Critical user story failed
- [ ] Data integrity compromised
- [ ] Security vulnerability detected
- [ ] Performance degradation > [X]%
- [ ] [Other criterion]
### Rollback Steps
1. [Command or process to rollback deployment]
2. [Verification step to confirm rollback]
3. [Communication plan - who to notify]
4. [Post-rollback validation]
### Post-Rollback Actions
- Document what failed and why
- Create incident report
- Plan fix and re-deployment
Phase 6: Review & Save
Present Draft to User
I've generated a production readiness checklist with:
- [N] user stories categorized by priority
- [N] acceptance criteria across all stories
- Production smoke tests
- Rollback plan
Review for completeness before I save.
Save Production Readiness Checklist
Save to docs/testplans/production-readiness-[feature-name].md
Summarize Next Steps
Production readiness checklist created at:
docs/testplans/production-readiness-[feature-name].md
Next steps:
1. Review with product owner and stakeholders
2. Execute all critical user story tests in staging
3. Run production smoke tests after deployment
4. Have rollback plan ready
5. Monitor production metrics during and after launch
Output Format Template
# Production Readiness: [Feature Name]
**Generated:** YYYY-MM-DD
**Target Launch Date:** YYYY-MM-DD
**Responsible Team:** [Team name]
**Production Environment:** [URL or platform]
---
## Executive Summary
**Feature Overview:** [Brief description]
**User Impact:** [Who is affected and how]
**Go/No-Go Criteria:** [What must pass for launch]
---
## User Stories & Acceptance Criteria
### Critical Stories (Must Pass for Launch)
#### 1. [User Story Title]
**As a** [user type]
**I want** [action]
**So that** [benefit]
**Acceptance Criteria:**
- [ ] [Criterion 1]
- [ ] [Criterion 2]
**Test Steps:**
1. [Step 1]
2. [Expected outcome]
**Dependencies:** [List]
---
### Important Stories (High Priority)
[Repeat format]
---
### Nice-to-Have Stories (Can Launch Without)
[Repeat format]
---
## Production Smoke Tests
Run immediately after deployment:
### Core Functionality
- [ ] [Test 1]
- [ ] [Test 2]
### Authentication & Authorization
- [ ] [Test 1]
### Data Integrity
- [ ] [Test 1]
### Integrations
- [ ] [Test 1]
### Performance
- [ ] [Test 1]
### Monitoring
- [ ] [Test 1]
---
## Rollback Plan
### Rollback Decision Criteria
- [ ] [Criterion 1]
### Rollback Steps
1. [Step 1]
### Post-Rollback Actions
- [Action 1]
---
## Sign-Off
- [ ] All critical user stories tested and passed
- [ ] Production smoke tests executed and passed
- [ ] Monitoring and alerting verified
- [ ] Rollback plan reviewed and ready
- [ ] Stakeholder approval obtained
**Ready for Production:** ☐ Yes ☐ No
**Sign-Off By:**
- Product Owner: _________________ Date: _______
- Engineering Lead: _________________ Date: _______
- QA Lead: _________________ Date: _______
---
*Production readiness checklist generated by agentbootup*
Key Principles
- Production-Focused: Every test must be relevant to production validation
- No Arbitrary Timeframes: Focus on criteria that must pass, not when testing happens
- Actionable Checklist: Every item should be testable and have clear pass/fail
- Risk-Aware: Prioritize by criticality and user impact
- Rollback-Ready: Always have a plan to undo if issues are found
Integration with Other Skills
- After prd-writer: Generate production readiness from PRD
- Before deployment: Use as pre-launch checklist
- With test-plan-generator: test-plan-generator is for feature E2E testing; production-readiness is for launch validation
- With runbook-generator: Reference production smoke tests in operational runbook
Target Audience
- Product owners deciding if feature is ready to launch
- QA teams validating production readiness
- Engineering leads signing off on deployments
- Stakeholders assessing go/no-go decisions
1---2name: production-readiness3description: Generate comprehensive pre-launch checklist of user stories, acceptance criteria, and smoke tests to validate before going live in production.4category: quality5metadata:6 source: https://skillmd.com/skills/dundas/production-readiness7---89# Production Readiness Generator1011## Goal12Create a comprehensive pre-launch checklist that outlines all user stories, acceptance criteria, and smoke tests that must pass before deploying to production.1314## Input Sources15- **PRD File** - Generate from `docs/prds/[n]-prd-*.md`16- **Feature Description** - Generate from verbal description17- **Existing User Stories** - Extract from project documentation1819## Output20- **Format:** Markdown (`.md`)21- **Location:** `docs/testplans/`22- **Filename:** `production-readiness-[feature-name].md`2324---2526## Process2728### Phase 1: Context Gathering29301. **Identify Input Source**31 - Check if user provided PRD, feature description, or reference to existing docs32 - If PRD: read and analyze user stories and acceptance criteria33 - If description: extract key functionality34 - If existing: scan docs for user story patterns35362. **GATE: Production Environment Confirmation**37 Ask the user:38 ```39 This checklist is for PRODUCTION deployment validation.4041 Please confirm:42 1. What is the current production environment? (URL, platform)43 2. When is the planned go-live date?44 3. Who is responsible for production deployment?45 4. What is the rollback procedure if issues are found?4647 Do NOT proceed without explicit confirmation.48 ```49503. **Gather Production Context**51 ```52 Additional production context needed:53 1. What is the user impact of this feature? (all users, subset, opt-in)54 2. Are there any compliance requirements? (GDPR, HIPAA, SOC2, etc.)55 3. What are the SLAs/performance requirements?56 4. What monitoring/alerting is in place?57 ```5859### Phase 2: User Story Extraction60614. **Map All User Stories**6263 Extract or generate complete set of user stories:6465 **From PRD/Documentation:**66 - Scan for "As a [user], I want [action], so that [benefit]" patterns67 - Extract acceptance criteria from requirements sections68 - Identify edge cases and error scenarios6970 **Generate if needed:**71 - Primary user flows (happy path)72 - Edge cases and error handling73 - Performance and scale scenarios74 - Security and compliance scenarios75 - Rollback and recovery scenarios76775. **Categorize User Stories**7879 Group by:80 - **Critical** - Must work for launch (blocking)81 - **Important** - Should work for launch (high priority)82 - **Nice-to-have** - Can work after launch (non-blocking)8384### Phase 3: Generate Acceptance Criteria85866. **Define Acceptance Criteria for Each Story**8788 For each user story, create specific, testable criteria:8990 ```markdown91 ### User Story: [Title]92 **As a** [user type]93 **I want** [action]94 **So that** [benefit]9596 **Priority:** Critical | Important | Nice-to-have9798 **Acceptance Criteria:**99 - [ ] [Specific, measurable criterion 1]100 - [ ] [Specific, measurable criterion 2]101 - [ ] [Error handling criterion]102 - [ ] [Performance criterion]103104 **Test Steps:**105 1. [Step 1]106 2. [Step 2]107 3. [Expected outcome]108109 **Dependencies:**110 - [Service, API, or feature this depends on]111 ```1121137. **Add Production-Specific Criteria**114115 For each story, add:116 - **Performance:** Response times, load handling117 - **Security:** Authentication, authorization, data protection118 - **Monitoring:** What metrics/logs to check119 - **Rollback:** How to undo if this fails120121### Phase 4: Generate Production Smoke Tests1221238. **Create Smoke Test Checklist**124125 ```markdown126 ## Production Smoke Tests127128 Run these tests IMMEDIATELY after deployment:129130 ### 1. Core Functionality131 - [ ] [Critical path 1]: [Expected outcome]132 - [ ] [Critical path 2]: [Expected outcome]133134 ### 2. Authentication & Authorization135 - [ ] Login works for all user types136 - [ ] Permissions are enforced correctly137 - [ ] Session management working138139 ### 3. Data Integrity140 - [ ] Data reads correctly from production DB141 - [ ] Data writes successfully142 - [ ] No data corruption or loss143144 ### 4. Integrations145 - [ ] External API calls succeed146 - [ ] Webhook deliveries working147 - [ ] Third-party services responding148149 ### 5. Performance150 - [ ] Page load times < [X]ms151 - [ ] API response times < [Y]ms152 - [ ] No memory leaks or resource exhaustion153154 ### 6. Monitoring & Alerting155 - [ ] Metrics being collected156 - [ ] Logs flowing correctly157 - [ ] Alerts configured and firing appropriately158 ```159160### Phase 5: Generate Rollback Plan1611629. **Document Rollback Procedures**163164 ```markdown165 ## Rollback Plan166167 If critical issues are found during validation:168169 ### Rollback Decision Criteria170 - [ ] Critical user story failed171 - [ ] Data integrity compromised172 - [ ] Security vulnerability detected173 - [ ] Performance degradation > [X]%174 - [ ] [Other criterion]175176 ### Rollback Steps177 1. [Command or process to rollback deployment]178 2. [Verification step to confirm rollback]179 3. [Communication plan - who to notify]180 4. [Post-rollback validation]181182 ### Post-Rollback Actions183 - Document what failed and why184 - Create incident report185 - Plan fix and re-deployment186 ```187188### Phase 6: Review & Save18919010. **Present Draft to User**191 ```192 I've generated a production readiness checklist with:193 - [N] user stories categorized by priority194 - [N] acceptance criteria across all stories195 - Production smoke tests196 - Rollback plan197198 Review for completeness before I save.199 ```20020111. **Save Production Readiness Checklist**202 Save to `docs/testplans/production-readiness-[feature-name].md`20320412. **Summarize Next Steps**205 ```206 Production readiness checklist created at:207 docs/testplans/production-readiness-[feature-name].md208209 Next steps:210 1. Review with product owner and stakeholders211 2. Execute all critical user story tests in staging212 3. Run production smoke tests after deployment213 4. Have rollback plan ready214 5. Monitor production metrics during and after launch215 ```216217---218219## Output Format Template220221```markdown222# Production Readiness: [Feature Name]223224**Generated:** YYYY-MM-DD225**Target Launch Date:** YYYY-MM-DD226**Responsible Team:** [Team name]227**Production Environment:** [URL or platform]228229---230231## Executive Summary232233**Feature Overview:** [Brief description]234**User Impact:** [Who is affected and how]235**Go/No-Go Criteria:** [What must pass for launch]236237---238239## User Stories & Acceptance Criteria240241### Critical Stories (Must Pass for Launch)242243#### 1. [User Story Title]244**As a** [user type]245**I want** [action]246**So that** [benefit]247248**Acceptance Criteria:**249- [ ] [Criterion 1]250- [ ] [Criterion 2]251252**Test Steps:**2531. [Step 1]2542. [Expected outcome]255256**Dependencies:** [List]257258---259260### Important Stories (High Priority)261262[Repeat format]263264---265266### Nice-to-Have Stories (Can Launch Without)267268[Repeat format]269270---271272## Production Smoke Tests273274Run immediately after deployment:275276### Core Functionality277- [ ] [Test 1]278- [ ] [Test 2]279280### Authentication & Authorization281- [ ] [Test 1]282283### Data Integrity284- [ ] [Test 1]285286### Integrations287- [ ] [Test 1]288289### Performance290- [ ] [Test 1]291292### Monitoring293- [ ] [Test 1]294295---296297## Rollback Plan298299### Rollback Decision Criteria300- [ ] [Criterion 1]301302### Rollback Steps3031. [Step 1]304305### Post-Rollback Actions306- [Action 1]307308---309310## Sign-Off311312- [ ] All critical user stories tested and passed313- [ ] Production smoke tests executed and passed314- [ ] Monitoring and alerting verified315- [ ] Rollback plan reviewed and ready316- [ ] Stakeholder approval obtained317318**Ready for Production:** ☐ Yes ☐ No319320**Sign-Off By:**321- Product Owner: _________________ Date: _______322- Engineering Lead: _________________ Date: _______323- QA Lead: _________________ Date: _______324325---326327*Production readiness checklist generated by agentbootup*328```329330---331332## Key Principles333334- **Production-Focused:** Every test must be relevant to production validation335- **No Arbitrary Timeframes:** Focus on criteria that must pass, not when testing happens336- **Actionable Checklist:** Every item should be testable and have clear pass/fail337- **Risk-Aware:** Prioritize by criticality and user impact338- **Rollback-Ready:** Always have a plan to undo if issues are found339340---341342## Integration with Other Skills343344- **After prd-writer:** Generate production readiness from PRD345- **Before deployment:** Use as pre-launch checklist346- **With test-plan-generator:** test-plan-generator is for feature E2E testing; production-readiness is for launch validation347- **With runbook-generator:** Reference production smoke tests in operational runbook348349---350351## Target Audience352353- Product owners deciding if feature is ready to launch354- QA teams validating production readiness355- Engineering leads signing off on deployments356- Stakeholders assessing go/no-go decisions