code-framework 1.0.0 → 1.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +99 -33
- package/_code/checklists/architecture-checklist.md +168 -0
- package/_code/checklists/brief-checklist.md +132 -0
- package/_code/checklists/code-review-checklist.md +211 -0
- package/_code/checklists/pre-release-checklist.md +248 -0
- package/_code/checklists/story-checklist.md +172 -0
- package/install.js +405 -103
- package/package.json +1 -1
- package/project-template/.claude/commands.yaml +228 -63
|
@@ -0,0 +1,248 @@
|
|
|
1
|
+
# Pre-Release Checklist
|
|
2
|
+
|
|
3
|
+
**Purpose:** Final validation before deploying to production.
|
|
4
|
+
|
|
5
|
+
**When to run:** Before any production deployment.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## 1. Feature Completeness
|
|
10
|
+
|
|
11
|
+
### User Stories
|
|
12
|
+
- [ ] **All stories complete** - Are all planned stories implemented?
|
|
13
|
+
- [ ] **AC verified** - Have all acceptance criteria been verified?
|
|
14
|
+
- [ ] **Edge cases tested** - Have edge cases been manually tested?
|
|
15
|
+
- [ ] **Stakeholder sign-off** - Has the product owner approved?
|
|
16
|
+
|
|
17
|
+
### Documentation
|
|
18
|
+
- [ ] **User docs updated** - Is user documentation current?
|
|
19
|
+
- [ ] **API docs updated** - Is API documentation complete?
|
|
20
|
+
- [ ] **Release notes drafted** - Are release notes prepared?
|
|
21
|
+
- [ ] **Changelog updated** - Is the changelog current?
|
|
22
|
+
|
|
23
|
+
---
|
|
24
|
+
|
|
25
|
+
## 2. Code Quality
|
|
26
|
+
|
|
27
|
+
### Testing
|
|
28
|
+
- [ ] **All tests passing** - Are all automated tests green?
|
|
29
|
+
- [ ] **Code coverage adequate** - Is coverage at acceptable level?
|
|
30
|
+
- [ ] **No skipped tests** - Are there unjustified skipped tests?
|
|
31
|
+
- [ ] **Performance tests passed** - Have load tests been run?
|
|
32
|
+
|
|
33
|
+
### Code Review
|
|
34
|
+
- [ ] **All PRs reviewed** - Has all code been reviewed?
|
|
35
|
+
- [ ] **No pending changes** - Are there no uncommitted changes?
|
|
36
|
+
- [ ] **Branch is clean** - Is the release branch up to date?
|
|
37
|
+
- [ ] **Conflicts resolved** - Are all merge conflicts resolved?
|
|
38
|
+
|
|
39
|
+
### Static Analysis
|
|
40
|
+
- [ ] **Linting passes** - Does code pass linting?
|
|
41
|
+
- [ ] **Type checking passes** - Does TypeScript compile?
|
|
42
|
+
- [ ] **No security warnings** - Does security scan pass?
|
|
43
|
+
- [ ] **Dependencies audited** - Are deps free of vulnerabilities?
|
|
44
|
+
|
|
45
|
+
---
|
|
46
|
+
|
|
47
|
+
## 3. Security
|
|
48
|
+
|
|
49
|
+
### Authentication
|
|
50
|
+
- [ ] **Auth flows tested** - Login/logout/signup working?
|
|
51
|
+
- [ ] **Password reset works** - Can users reset passwords?
|
|
52
|
+
- [ ] **Session management** - Are sessions handled properly?
|
|
53
|
+
- [ ] **OAuth/SSO tested** - Are third-party auth flows working?
|
|
54
|
+
|
|
55
|
+
### Authorization
|
|
56
|
+
- [ ] **Permissions enforced** - Are role restrictions working?
|
|
57
|
+
- [ ] **Admin functions secured** - Are admin actions protected?
|
|
58
|
+
- [ ] **Data isolation verified** - Can users only see their data?
|
|
59
|
+
- [ ] **API auth required** - Are all endpoints properly secured?
|
|
60
|
+
|
|
61
|
+
### Data Protection
|
|
62
|
+
- [ ] **HTTPS enforced** - Is HTTPS required everywhere?
|
|
63
|
+
- [ ] **Sensitive data encrypted** - Is PII properly protected?
|
|
64
|
+
- [ ] **Secrets rotated** - Are production secrets fresh?
|
|
65
|
+
- [ ] **Security headers set** - Are headers configured?
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
69
|
+
## 4. Performance
|
|
70
|
+
|
|
71
|
+
### Frontend
|
|
72
|
+
- [ ] **Page load times acceptable** - Are pages loading fast enough?
|
|
73
|
+
- [ ] **Lighthouse scores good** - Performance/accessibility scores OK?
|
|
74
|
+
- [ ] **Images optimized** - Are images properly optimized?
|
|
75
|
+
- [ ] **Bundle size acceptable** - Is JS bundle size reasonable?
|
|
76
|
+
|
|
77
|
+
### Backend
|
|
78
|
+
- [ ] **API response times** - Are endpoints responding quickly?
|
|
79
|
+
- [ ] **Database queries optimized** - Are slow queries addressed?
|
|
80
|
+
- [ ] **Caching working** - Is caching functioning properly?
|
|
81
|
+
- [ ] **No memory leaks** - Is memory usage stable?
|
|
82
|
+
|
|
83
|
+
### Scalability
|
|
84
|
+
- [ ] **Load testing passed** - Has the app been load tested?
|
|
85
|
+
- [ ] **Auto-scaling configured** - Will it scale under load?
|
|
86
|
+
- [ ] **Database can handle load** - Is database scaled properly?
|
|
87
|
+
- [ ] **Rate limiting active** - Are rate limits configured?
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
91
|
+
## 5. Infrastructure
|
|
92
|
+
|
|
93
|
+
### Environment
|
|
94
|
+
- [ ] **Staging tested** - Has staging been thoroughly tested?
|
|
95
|
+
- [ ] **Environment parity** - Does staging match production?
|
|
96
|
+
- [ ] **Config validated** - Are production configs correct?
|
|
97
|
+
- [ ] **Secrets configured** - Are all secrets in place?
|
|
98
|
+
|
|
99
|
+
### Database
|
|
100
|
+
- [ ] **Migrations ready** - Are DB migrations tested?
|
|
101
|
+
- [ ] **Backup verified** - Is database backup recent and tested?
|
|
102
|
+
- [ ] **Rollback plan** - Can migrations be reversed?
|
|
103
|
+
- [ ] **Data seeded** - Is initial data in place?
|
|
104
|
+
|
|
105
|
+
### Services
|
|
106
|
+
- [ ] **Third-party services** - Are external services configured?
|
|
107
|
+
- [ ] **API keys set** - Are all API keys in production?
|
|
108
|
+
- [ ] **Webhooks configured** - Are webhooks pointing to production?
|
|
109
|
+
- [ ] **Email/SMS working** - Are notification services set up?
|
|
110
|
+
|
|
111
|
+
---
|
|
112
|
+
|
|
113
|
+
## 6. Monitoring & Alerting
|
|
114
|
+
|
|
115
|
+
### Logging
|
|
116
|
+
- [ ] **Application logs** - Is logging configured?
|
|
117
|
+
- [ ] **Error tracking** - Are errors being captured?
|
|
118
|
+
- [ ] **Audit logging** - Are sensitive actions logged?
|
|
119
|
+
- [ ] **Log retention** - Is log retention configured?
|
|
120
|
+
|
|
121
|
+
### Monitoring
|
|
122
|
+
- [ ] **Health checks** - Are health endpoints working?
|
|
123
|
+
- [ ] **Uptime monitoring** - Is uptime being tracked?
|
|
124
|
+
- [ ] **Performance monitoring** - Are metrics being collected?
|
|
125
|
+
- [ ] **User monitoring** - Is user behavior being tracked (if needed)?
|
|
126
|
+
|
|
127
|
+
### Alerting
|
|
128
|
+
- [ ] **Error alerts** - Will you be notified of errors?
|
|
129
|
+
- [ ] **Downtime alerts** - Will you know if the app goes down?
|
|
130
|
+
- [ ] **Performance alerts** - Will you be warned of slowdowns?
|
|
131
|
+
- [ ] **Security alerts** - Will you be notified of security events?
|
|
132
|
+
|
|
133
|
+
---
|
|
134
|
+
|
|
135
|
+
## 7. Deployment
|
|
136
|
+
|
|
137
|
+
### Process
|
|
138
|
+
- [ ] **Deployment documented** - Is the process documented?
|
|
139
|
+
- [ ] **CI/CD configured** - Is automated deployment ready?
|
|
140
|
+
- [ ] **Blue-green/canary** - Is deployment strategy defined?
|
|
141
|
+
- [ ] **Zero downtime** - Will deployment avoid downtime?
|
|
142
|
+
|
|
143
|
+
### Rollback
|
|
144
|
+
- [ ] **Rollback documented** - Is rollback process clear?
|
|
145
|
+
- [ ] **Rollback tested** - Has rollback been practiced?
|
|
146
|
+
- [ ] **Feature flags ready** - Can features be disabled quickly?
|
|
147
|
+
- [ ] **Previous version available** - Can you restore previous version?
|
|
148
|
+
|
|
149
|
+
### Communication
|
|
150
|
+
- [ ] **Stakeholders notified** - Is the team aware of release?
|
|
151
|
+
- [ ] **Support ready** - Is support team prepared?
|
|
152
|
+
- [ ] **Status page ready** - Can you communicate status?
|
|
153
|
+
- [ ] **Maintenance window** - Is timing communicated?
|
|
154
|
+
|
|
155
|
+
---
|
|
156
|
+
|
|
157
|
+
## 8. Post-Release
|
|
158
|
+
|
|
159
|
+
### Verification
|
|
160
|
+
- [ ] **Smoke tests planned** - What will you test first?
|
|
161
|
+
- [ ] **Success criteria** - How will you know it's working?
|
|
162
|
+
- [ ] **Rollback triggers** - When will you rollback?
|
|
163
|
+
- [ ] **Monitoring period** - How long will you watch closely?
|
|
164
|
+
|
|
165
|
+
### Support
|
|
166
|
+
- [ ] **On-call assigned** - Who's watching the release?
|
|
167
|
+
- [ ] **Escalation path** - Who to contact for issues?
|
|
168
|
+
- [ ] **Known issues documented** - Are workarounds documented?
|
|
169
|
+
- [ ] **FAQ prepared** - Are common questions answered?
|
|
170
|
+
|
|
171
|
+
---
|
|
172
|
+
|
|
173
|
+
## Risk Assessment
|
|
174
|
+
|
|
175
|
+
### Known Risks
|
|
176
|
+
List identified risks and their mitigations:
|
|
177
|
+
1.
|
|
178
|
+
2.
|
|
179
|
+
3.
|
|
180
|
+
|
|
181
|
+
### Incomplete Items
|
|
182
|
+
List anything incomplete that's being released anyway:
|
|
183
|
+
1.
|
|
184
|
+
2.
|
|
185
|
+
3.
|
|
186
|
+
|
|
187
|
+
### Dependencies
|
|
188
|
+
List external dependencies that could cause issues:
|
|
189
|
+
1.
|
|
190
|
+
2.
|
|
191
|
+
3.
|
|
192
|
+
|
|
193
|
+
---
|
|
194
|
+
|
|
195
|
+
## Overall Assessment
|
|
196
|
+
|
|
197
|
+
### Completeness Score
|
|
198
|
+
Count the checked items above: ____ / 85
|
|
199
|
+
|
|
200
|
+
### Scoring Guide
|
|
201
|
+
- **76-85**: GO - Ready for production release
|
|
202
|
+
- **65-75**: CONDITIONAL GO - Can release with documented risks
|
|
203
|
+
- **55-64**: HOLD - Address critical issues before release
|
|
204
|
+
- **Below 55**: NO GO - Not ready for production
|
|
205
|
+
|
|
206
|
+
### Critical Blockers
|
|
207
|
+
Issues that must be resolved before release:
|
|
208
|
+
1.
|
|
209
|
+
2.
|
|
210
|
+
3.
|
|
211
|
+
|
|
212
|
+
### Accepted Risks
|
|
213
|
+
Risks accepted for this release:
|
|
214
|
+
1.
|
|
215
|
+
2.
|
|
216
|
+
3.
|
|
217
|
+
|
|
218
|
+
---
|
|
219
|
+
|
|
220
|
+
## Sign-Off
|
|
221
|
+
|
|
222
|
+
### Release Decision
|
|
223
|
+
|
|
224
|
+
- [ ] **GO** - Approved for production release
|
|
225
|
+
- [ ] **CONDITIONAL GO** - Approved with noted conditions
|
|
226
|
+
- [ ] **HOLD** - Release postponed pending fixes
|
|
227
|
+
- [ ] **NO GO** - Release cancelled
|
|
228
|
+
|
|
229
|
+
**Release Manager:**
|
|
230
|
+
|
|
231
|
+
**Date:**
|
|
232
|
+
|
|
233
|
+
**Version:**
|
|
234
|
+
|
|
235
|
+
**Notes:**
|
|
236
|
+
|
|
237
|
+
---
|
|
238
|
+
|
|
239
|
+
## Post-Release Notes
|
|
240
|
+
|
|
241
|
+
### What Went Well
|
|
242
|
+
|
|
243
|
+
|
|
244
|
+
### What Could Improve
|
|
245
|
+
|
|
246
|
+
|
|
247
|
+
### Action Items for Next Release
|
|
248
|
+
|
|
@@ -0,0 +1,172 @@
|
|
|
1
|
+
# Story Quality Checklist
|
|
2
|
+
|
|
3
|
+
**Purpose:** Validate that a user story is ready for implementation.
|
|
4
|
+
|
|
5
|
+
**When to run:** Before starting implementation of any story.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## 1. Story Structure
|
|
10
|
+
|
|
11
|
+
### Title & Description
|
|
12
|
+
- [ ] **Clear title** - Is the story title descriptive and concise?
|
|
13
|
+
- [ ] **User story format** - "As a [user], I want [goal], so that [benefit]"?
|
|
14
|
+
- [ ] **Context provided** - Is background information included?
|
|
15
|
+
- [ ] **Epic reference** - Is the parent epic clearly identified?
|
|
16
|
+
|
|
17
|
+
### Metadata
|
|
18
|
+
- [ ] **Story ID** - Unique identifier present?
|
|
19
|
+
- [ ] **Priority** - P0/P1/P2 clearly marked?
|
|
20
|
+
- [ ] **Estimate** - Size/complexity estimated (S/M/L/XL)?
|
|
21
|
+
- [ ] **Dependencies** - Are blocking stories identified?
|
|
22
|
+
|
|
23
|
+
---
|
|
24
|
+
|
|
25
|
+
## 2. Acceptance Criteria Quality
|
|
26
|
+
|
|
27
|
+
### Completeness
|
|
28
|
+
- [ ] **AC defined** - Are acceptance criteria clearly listed?
|
|
29
|
+
- [ ] **All scenarios covered** - Happy path AND edge cases?
|
|
30
|
+
- [ ] **Testable criteria** - Can each AC be verified?
|
|
31
|
+
- [ ] **No ambiguity** - Is each AC specific and measurable?
|
|
32
|
+
|
|
33
|
+
### Format
|
|
34
|
+
- [ ] **Given-When-Then** - Are criteria in BDD format where helpful?
|
|
35
|
+
- [ ] **Numbered/bulleted** - Are criteria easy to track?
|
|
36
|
+
- [ ] **Independent** - Can each criterion be verified separately?
|
|
37
|
+
|
|
38
|
+
### Coverage
|
|
39
|
+
- [ ] **UI behavior** - Is the expected UI behavior described?
|
|
40
|
+
- [ ] **Error handling** - What happens when things go wrong?
|
|
41
|
+
- [ ] **Edge cases** - Are boundary conditions addressed?
|
|
42
|
+
- [ ] **Permissions** - Who can perform this action?
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
46
|
+
## 3. Technical Guidance
|
|
47
|
+
|
|
48
|
+
### Implementation Hints
|
|
49
|
+
- [ ] **Files to modify** - Are target files/components identified?
|
|
50
|
+
- [ ] **Patterns to follow** - Are existing patterns referenced?
|
|
51
|
+
- [ ] **Anti-patterns** - Are things to avoid mentioned?
|
|
52
|
+
- [ ] **Dependencies** - Are required packages/services listed?
|
|
53
|
+
|
|
54
|
+
### Architecture Alignment
|
|
55
|
+
- [ ] **Follows architecture** - Does it align with technical outline?
|
|
56
|
+
- [ ] **No scope creep** - Does it stay within the story's scope?
|
|
57
|
+
- [ ] **Reuses existing** - Does it leverage existing code where possible?
|
|
58
|
+
|
|
59
|
+
### Data Requirements
|
|
60
|
+
- [ ] **Schema changes** - Are any database changes needed?
|
|
61
|
+
- [ ] **API changes** - Are API modifications documented?
|
|
62
|
+
- [ ] **Migrations** - Are data migrations required?
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## 4. Testing Requirements
|
|
67
|
+
|
|
68
|
+
### Test Coverage
|
|
69
|
+
- [ ] **Unit tests** - Are unit test expectations defined?
|
|
70
|
+
- [ ] **Integration tests** - Are integration tests needed?
|
|
71
|
+
- [ ] **E2E tests** - Are end-to-end tests required?
|
|
72
|
+
- [ ] **Manual testing** - Is manual testing checklist included?
|
|
73
|
+
|
|
74
|
+
### Test Scenarios
|
|
75
|
+
- [ ] **Happy path** - Is the main success scenario testable?
|
|
76
|
+
- [ ] **Error cases** - Are error scenarios identified for testing?
|
|
77
|
+
- [ ] **Edge cases** - Are boundary tests specified?
|
|
78
|
+
- [ ] **Regression** - Are regression test areas identified?
|
|
79
|
+
|
|
80
|
+
---
|
|
81
|
+
|
|
82
|
+
## 5. UX Requirements
|
|
83
|
+
|
|
84
|
+
### Design Reference
|
|
85
|
+
- [ ] **Wireframe linked** - Is there a wireframe reference?
|
|
86
|
+
- [ ] **Design specs** - Are design details documented?
|
|
87
|
+
- [ ] **Responsive** - Are mobile/desktop behaviors specified?
|
|
88
|
+
- [ ] **Accessibility** - Are a11y requirements noted?
|
|
89
|
+
|
|
90
|
+
### User Experience
|
|
91
|
+
- [ ] **Loading states** - What shows during async operations?
|
|
92
|
+
- [ ] **Empty states** - What shows when there's no data?
|
|
93
|
+
- [ ] **Error states** - What shows when errors occur?
|
|
94
|
+
- [ ] **Success feedback** - How does the user know it worked?
|
|
95
|
+
|
|
96
|
+
---
|
|
97
|
+
|
|
98
|
+
## 6. Dependencies & Risks
|
|
99
|
+
|
|
100
|
+
### Prerequisites
|
|
101
|
+
- [ ] **Blocking stories** - Are dependencies on other stories clear?
|
|
102
|
+
- [ ] **External deps** - Are third-party dependencies identified?
|
|
103
|
+
- [ ] **Environment needs** - Any special environment requirements?
|
|
104
|
+
|
|
105
|
+
### Risks
|
|
106
|
+
- [ ] **Technical risks** - Are known technical risks documented?
|
|
107
|
+
- [ ] **Business risks** - Are stakeholder concerns noted?
|
|
108
|
+
- [ ] **Mitigation** - Are risk mitigation strategies suggested?
|
|
109
|
+
|
|
110
|
+
---
|
|
111
|
+
|
|
112
|
+
## 7. Definition of Done
|
|
113
|
+
|
|
114
|
+
### Code Quality
|
|
115
|
+
- [ ] **Code complete** - All acceptance criteria implemented?
|
|
116
|
+
- [ ] **Tests passing** - All tests written and passing?
|
|
117
|
+
- [ ] **No linting errors** - Code passes linting?
|
|
118
|
+
- [ ] **Code reviewed** - PR reviewed and approved?
|
|
119
|
+
|
|
120
|
+
### Documentation
|
|
121
|
+
- [ ] **Code documented** - Are complex parts documented?
|
|
122
|
+
- [ ] **API documented** - Are new APIs documented?
|
|
123
|
+
- [ ] **Changelog updated** - Is the change logged?
|
|
124
|
+
|
|
125
|
+
### Deployment
|
|
126
|
+
- [ ] **Environment tested** - Tested in staging/preview?
|
|
127
|
+
- [ ] **No regressions** - Existing functionality still works?
|
|
128
|
+
- [ ] **Rollback plan** - Can this be reverted if needed?
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
|
|
132
|
+
## Overall Assessment
|
|
133
|
+
|
|
134
|
+
### Completeness Score
|
|
135
|
+
Count the checked items above: ____ / 50
|
|
136
|
+
|
|
137
|
+
### Scoring Guide
|
|
138
|
+
- **45-50**: Excellent - Ready for implementation
|
|
139
|
+
- **38-44**: Good - Minor gaps, can proceed
|
|
140
|
+
- **30-37**: Fair - Should improve before starting
|
|
141
|
+
- **Below 30**: Incomplete - Story needs more work
|
|
142
|
+
|
|
143
|
+
### Blockers (Must Fix)
|
|
144
|
+
List issues that would block implementation:
|
|
145
|
+
1.
|
|
146
|
+
2.
|
|
147
|
+
3.
|
|
148
|
+
|
|
149
|
+
### Ambiguities
|
|
150
|
+
List areas needing clarification:
|
|
151
|
+
1.
|
|
152
|
+
2.
|
|
153
|
+
3.
|
|
154
|
+
|
|
155
|
+
### Missing Information
|
|
156
|
+
List information that should be added:
|
|
157
|
+
1.
|
|
158
|
+
2.
|
|
159
|
+
3.
|
|
160
|
+
|
|
161
|
+
---
|
|
162
|
+
|
|
163
|
+
## Verdict
|
|
164
|
+
|
|
165
|
+
**Ready for implementation?**
|
|
166
|
+
|
|
167
|
+
- [ ] **YES** - Story is well-defined and implementable
|
|
168
|
+
- [ ] **YES, WITH NOTES** - Minor clarifications noted, can proceed
|
|
169
|
+
- [ ] **NO** - Story needs refinement first
|
|
170
|
+
|
|
171
|
+
**Reviewer notes:**
|
|
172
|
+
|