@codihaus/claude-skills 1.6.6 → 1.6.8

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.
@@ -39,255 +39,101 @@ plans/features/{feature}/
39
39
  └── docs-updates.md # Documentation tasks
40
40
  ```
41
41
 
42
- ## Workflow
42
+ ## Expected Outcome
43
43
 
44
- ### Phase 0: Verify Review Passed
44
+ Documentation of what was implemented after `/dev-review` passes.
45
45
 
46
- ```
47
- 1. Check: Did /dev-review pass?
48
- Look for review output
49
- Check git for recent review commits
46
+ **Outputs:**
47
+ - `summary.md` - What was built this session/PR
48
+ - `implementation.md` - Cumulative status (updated)
49
+ - `tech-debt.md` - Known issues, TODOs (updated)
50
+ - `docs-updates.md` - Documentation tasks
50
51
 
51
- 2. If review not done or failed:
52
- → "Run /dev-review first"
53
- → Exit
54
- ```
52
+ ## Success Criteria
55
53
 
56
- ### Phase 1: Gather Sources
54
+ - Changes mapped to specs and use cases
55
+ - Completion status clear (done/partial/not started)
56
+ - Tech debt captured (TODOs, workarounds, gaps)
57
+ - Documentation tasks identified
58
+ - Easy to resume work later
59
+ - Clear what's done, what's remaining
57
60
 
58
- ```
59
- 1. Git changes (source of truth)
60
- git log --oneline {since}
61
- git diff --stat {since}
61
+ ## Prerequisite
62
62
 
63
- 2. PR/MR info (if available)
64
- gh pr view {number}
63
+ **Verify `/dev-review` passed:**
64
+ - If review not done or failed → "Run /dev-review first"
65
65
 
66
- 3. Specs (intent)
67
- plans/features/{feature}/specs/*.md
66
+ ## Sources to Gather
68
67
 
69
- 4. Use cases (context)
70
- plans/brd/use-cases/{feature}/*.md
68
+ **Git (source of truth):**
69
+ - `git log --oneline {since}` - Commits made
70
+ - `git diff --stat {since}` - Files changed
71
+ - `gh pr view {number}` - PR info (if available)
71
72
 
72
- 5. Previous implementation status
73
- plans/features/{feature}/implementation.md
74
- ```
73
+ **Intent & Context:**
74
+ - specs/*.md - What was intended
75
+ - use-cases/*.md - Business context
76
+ - implementation.md (previous) - Track cumulative status
75
77
 
76
- ### Phase 2: Analyze Changes
78
+ ## Analysis
77
79
 
78
- Map git changes to specs and use cases:
80
+ **Map git changes to specs and use cases:**
79
81
 
80
- ```
81
82
  For each changed file:
82
- 1. What component is this? (API, UI, model, etc.)
83
- 2. Which spec item does it fulfill?
84
- 3. Which use case does it support?
85
- 4. Is it complete or partial?
86
- ```
87
-
88
- **Mapping table:**
83
+ - What component? (API, UI, model, etc.)
84
+ - Which spec item does it fulfill?
85
+ - Which use case does it support?
86
+ - Complete or partial?
89
87
 
90
- | File Changed | Type | Spec Item | Use Case | Status |
91
- |--------------|------|-----------|----------|--------|
92
- | `api/billing/checkout.ts` | API | SPEC-PAY-001 | UC-PAY-001 | Complete |
93
- | `components/CheckoutForm.tsx` | UI | SPEC-PAY-001 | UC-PAY-001 | Complete |
94
- | `api/billing/subscription.ts` | API | SPEC-PAY-004 | UC-PAY-002 | Partial |
88
+ **Extract tech debt:**
89
+ - TODOs in changed files (grep for TODO/FIXME/HACK/XXX)
90
+ - Incomplete spec items (spec says X, implementation does Y)
91
+ - Known issues from commits (WIP, temporary, workaround)
92
+ - Review comments not addressed
95
93
 
96
- ### Phase 3: Extract Tech Debt
94
+ **Identify doc updates needed:**
97
95
 
98
- Scan for incomplete items:
99
-
100
- ```
101
- 1. TODOs in changed files
102
- grep -r "TODO\|FIXME\|HACK\|XXX" {changed_files}
103
-
104
- 2. Incomplete spec items
105
- → Spec says X, implementation does Y
106
-
107
- 3. Known issues from commits
108
- → "WIP:", "temporary", "workaround"
109
-
110
- 4. Review comments not addressed
111
- → From /dev-review output
112
- ```
113
-
114
- ### Phase 4: Identify Documentation Updates
115
-
116
- Based on what changed:
117
-
118
- | Change Type | Doc Update Needed |
119
- |-------------|-------------------|
96
+ | Change Type | Doc Update |
97
+ |-------------|------------|
120
98
  | New API endpoint | API Reference |
121
99
  | New UI feature | User Guide |
122
100
  | New config option | Configuration docs |
123
101
  | Breaking change | Migration guide |
124
102
  | New component | Component docs |
125
103
 
126
- ### Phase 5: Generate Outputs
127
-
128
- #### summary.md (per session/PR)
129
-
130
- ```markdown
131
- # Summary: {Feature} - {Date/PR}
132
-
133
- > **PR**: #{number} or commit range
134
- > **Author**: {who}
135
- > **Review**: Passed
136
-
137
- ## What Was Built
138
-
139
- ### API Changes
140
- - `POST /api/billing/checkout` - Process payment
141
- - `GET /api/billing/invoices` - List invoices
142
-
143
- ### UI Changes
144
- - CheckoutForm component
145
- - InvoiceList component
146
- - PaymentSuccess page
147
-
148
- ### Data Changes
149
- - Added Invoice model
150
- - Added Payment model
151
- - Migration: 20240118_add_billing_tables
152
-
153
- ## Spec Items Completed
154
-
155
- | Spec | Title | Status |
156
- |------|-------|--------|
157
- | SPEC-PAY-001 | Checkout Flow | ✅ Complete |
158
- | SPEC-PAY-002 | Payment Processing | ✅ Complete |
159
- | SPEC-PAY-004 | Subscription Mgmt | ⚠️ Partial |
160
-
161
- ## Use Cases Addressed
162
-
163
- | UC | Title | Coverage |
164
- |----|-------|----------|
165
- | UC-PAY-001 | Checkout | Full |
166
- | UC-PAY-002 | Subscribe | Create only |
167
-
168
- ## Commits
169
-
170
- - `abc1234` feat(billing): add checkout endpoint
171
- - `def5678` feat(billing): add CheckoutForm component
172
- - `ghi9012` feat(billing): add invoice model
173
-
174
- ## Next Steps
175
-
176
- 1. Complete subscription upgrade/downgrade (SPEC-PAY-004)
177
- 2. Add refund functionality (SPEC-PAY-005)
178
- 3. Update API documentation
179
- ```
180
-
181
- #### implementation.md (cumulative status)
104
+ ## Output Files
182
105
 
183
- ```markdown
184
- # Implementation Status: {Feature}
106
+ **summary.md** (per session/PR):
107
+ - What was built (API, UI, data changes)
108
+ - Spec items completed (with status)
109
+ - Use cases addressed (coverage)
110
+ - Commits list
111
+ - Next steps
185
112
 
186
- > **Last Updated**: {date}
187
- > **Overall Progress**: 60% (3/5 specs complete)
113
+ **implementation.md** (cumulative):
114
+ - Overall progress percentage
115
+ - Completed items (with PR reference)
116
+ - In progress items (what's done, what's remaining)
117
+ - Not started items (with blockers if any)
118
+ - History (date, PR, summary)
188
119
 
189
- ## Completed ✅
120
+ **tech-debt.md** (updated):
121
+ - High/Medium/Low priority issues
122
+ - Location, impact, notes for each
123
+ - Code TODOs with file:line references
190
124
 
191
- | Item | Spec | UC | Implemented In |
192
- |------|------|----|----------------|
193
- | Checkout | SPEC-PAY-001 | UC-PAY-001 | PR #123 |
194
- | Payments | SPEC-PAY-002 | UC-PAY-001 | PR #123 |
195
- | Invoices | SPEC-PAY-003 | UC-PAY-003 | PR #125 |
125
+ **docs-updates.md** (updated):
126
+ - Required updates (API Reference, User Guide, Configuration)
127
+ - Examples to add (code snippets)
128
+ - Screenshots needed
196
129
 
197
- ## In Progress ⚠️
198
-
199
- | Item | Spec | UC | Done | Remaining |
200
- |------|------|----|------|-----------|
201
- | Subscriptions | SPEC-PAY-004 | UC-PAY-002 | Create/cancel | Upgrade/downgrade |
202
-
203
- ## Not Started ❌
204
-
205
- | Item | Spec | UC | Blocked By |
206
- |------|------|----|------------|
207
- | Refunds | SPEC-PAY-005 | UC-PAY-004 | - |
208
- | Usage billing | SPEC-PAY-006 | UC-PAY-005 | Phase 2 |
209
-
210
- ## History
211
-
212
- | Date | PR | Summary |
213
- |------|----|---------|
214
- | 2024-01-18 | #123 | Checkout + payments |
215
- | 2024-01-20 | #125 | Invoice generation |
216
- ```
217
-
218
- #### tech-debt.md
219
-
220
- ```markdown
221
- # Tech Debt: {Feature}
222
-
223
- > **Last Updated**: {date}
224
-
225
- ## High Priority
226
-
227
- | Issue | Location | Impact | Notes |
228
- |-------|----------|--------|-------|
229
- | No retry on payment failure | `billing/stripe.ts:45` | Users see errors | Add exponential backoff |
230
-
231
- ## Medium Priority
232
-
233
- | Issue | Location | Impact | Notes |
234
- |-------|----------|--------|-------|
235
- | Hardcoded tax rate | `billing/invoice.ts:23` | Wrong tax for some regions | Make configurable |
236
- | No pagination | `api/invoices.ts:12` | Slow for many invoices | Add cursor pagination |
237
-
238
- ## Low Priority
239
-
240
- | Issue | Location | Impact | Notes |
241
- |-------|----------|--------|-------|
242
- | TODO: Add logging | `billing/checkout.ts:78` | Hard to debug | Add structured logging |
243
-
244
- ## Code TODOs
245
-
246
- ```
247
- billing/stripe.ts:45: TODO: Add retry logic for failed payments
248
- billing/invoice.ts:23: TODO: Make tax rate configurable
249
- billing/checkout.ts:78: TODO: Add logging
250
- ```
251
- ```
252
-
253
- #### docs-updates.md
254
-
255
- ```markdown
256
- # Documentation Updates: {Feature}
257
-
258
- > **Last Updated**: {date}
259
-
260
- ## Required Updates
261
-
262
- ### API Reference
263
- - [ ] Add `POST /api/billing/checkout` endpoint
264
- - [ ] Add `GET /api/billing/invoices` endpoint
265
- - [ ] Add `POST /api/billing/subscriptions` endpoint
266
-
267
- ### User Guide
268
- - [ ] Add "Making a Purchase" section
269
- - [ ] Add "Managing Your Subscription" section
270
- - [ ] Add "Viewing Invoices" section
271
-
272
- ### Configuration
273
- - [ ] Document `STRIPE_SECRET_KEY` env var
274
- - [ ] Document `STRIPE_WEBHOOK_SECRET` env var
275
-
276
- ## Examples to Add
277
-
278
- ### API Examples
279
- ```bash
280
- # Checkout
281
- curl -X POST /api/billing/checkout \
282
- -H "Authorization: Bearer {token}" \
283
- -d '{"planId": "pro", "paymentMethodId": "pm_xxx"}'
284
- ```
130
+ ## Resume Flow
285
131
 
286
- ### UI Screenshots Needed
287
- - [ ] Checkout form
288
- - [ ] Payment success page
289
- - [ ] Invoice list
290
- ```
132
+ When returning to work later:
133
+ 1. Read implementation.md See what's done, what's remaining
134
+ 2. Read tech-debt.md See known issues
135
+ 3. Read summary.md (latest) → See where you left off
136
+ 4. Continue with `/dev-specs` or `/dev-coding`
291
137
 
292
138
  ## Integration with /dev-review
293
139