@codihaus/claude-skills 1.6.24 → 1.6.25

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@codihaus/claude-skills",
3
- "version": "1.6.24",
3
+ "version": "1.6.25",
4
4
  "description": "Claude Code skills for software development workflow",
5
5
  "main": "src/index.js",
6
6
  "bin": {
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: debrief
3
3
  description: Customer requirements → market-validated BRD with tiered features
4
- version: 4.2.0
4
+ version: 5.0.0
5
5
  ---
6
6
 
7
7
  # /debrief - Business Requirements Document
@@ -78,22 +78,26 @@ version: 4.2.0
78
78
 
79
79
  **If you mention files, code, APIs, or tech → YOU ARE DOING IT WRONG.**
80
80
 
81
- ### 3. Comparison-First Research
81
+ ### 3. Deep Research (Always)
82
82
 
83
- Use comparison pages first (5-10 competitors in one page):
84
- - `"{category} comparison"`
85
- - `"best {category} alternatives"`
83
+ **Always thorough**:
84
+ - Comparison pages (feature matrix)
85
+ - Ecosystems (Chrome, WordPress, GitHub)
86
+ - User signals (Reddit, reviews, forums)
87
+ - Full evidence per feature
86
88
 
87
- Then validate per feature (Quick or Deep).
89
+ No quick mode. Always deep.
88
90
 
89
- ### 4. Questionnaire = Research Output
91
+ ### 4. Questionnaire = Decision Tool
90
92
 
91
- **3 sheets**:
92
- - Summary (stats, tiers)
93
+ **3 sheets with evidence**:
94
+ - Summary (features count, tier breakdown, research stats)
93
95
  - Questions (validation + open)
94
- - References (URLs)
96
+ - References (URLs, evidence per feature)
95
97
 
96
- Customer reviews, answers, returns file. Then create BRD via `--answers`.
98
+ **Purpose**: User reviews evidence, makes decisions, validates with customer.
99
+
100
+ Then create BRD via `--answers` or `--generate-brd`.
97
101
 
98
102
  ---
99
103
 
@@ -110,11 +114,11 @@ Customer reviews, answers, returns file. Then create BRD via `--answers`.
110
114
 
111
115
  ---
112
116
 
113
- ## Market Research
117
+ ## Market Research (Always Deep)
114
118
 
115
- **See** `references/market-research-methodology.md`.
119
+ **See** `references/research.md`.
116
120
 
117
- **Sources**: Competitors, ecosystems (Chrome, WordPress, GitHub, etc.), user signals (Reddit, reviews).
121
+ **Always deep**: Comparison + ecosystems + user signals + full evidence.
118
122
 
119
123
  **Tiers**:
120
124
  - **MVP**: 80%+ competitors, free tier, high demand
@@ -2,9 +2,9 @@
2
2
 
3
3
  **Mindset**: Business analyst. Focus on WHAT and WHY, defer HOW to /dev-specs.
4
4
 
5
- **Methodology**: Mode detection → Context gathering → Research Document → Questionnaire
5
+ **Methodology**: Mode detection → Context gathering → Research (deep) → Questionnaire
6
6
 
7
- **Expected Outcome**: Market-validated BRD with tiered features, lean use cases, customer questionnaire.
7
+ **Expected Outcome**: Questionnaire with deep research evidence (Summary + Questions + References).
8
8
 
9
9
  ---
10
10
 
@@ -37,13 +37,12 @@
37
37
  - Reuse → Switch to Generate BRD mode
38
38
  - Fresh → Continue with new research
39
39
 
40
- **Ask 6 questions** (AskUserQuestion):
40
+ **Ask 5 questions** (AskUserQuestion):
41
41
  1. Project type (new/existing codebase)
42
42
  2. Industry (SaaS/E-commerce/Marketplace/etc.)
43
43
  3. Target users (B2B/B2C/Internal)
44
44
  4. Constraints (timeline/budget/compliance/integrations)
45
45
  5. Scope tier (Core/Standard/Full)
46
- 6. Research depth (Quick 5min / Deep 15-20min)
47
46
 
48
47
  **If existing codebase**: Scan for docs + features (Glob, Read)
49
48
 
@@ -51,79 +50,20 @@
51
50
 
52
51
  ---
53
52
 
54
- ### Market Research
53
+ ### Market Research (Always Deep)
55
54
 
56
55
  **Methodology**: See `research.md` for full process.
57
56
 
58
- **Quick** (5 min):
59
- - Find 2-3 comparison/alternative pages
60
- - Extract feature matrix
61
- - Initial tier hypothesis
62
-
63
- **Deep** (15-20 min):
64
- - Comparison pages (initial)
65
- - Cross-validate with ecosystem + user signals
66
- - Full tier classification with evidence
57
+ **Deep research** (always):
58
+ 1. Comparison pages (feature matrix extraction)
59
+ 2. Ecosystems (Chrome, WordPress, GitHub, etc.)
60
+ 3. User signals (Reddit, reviews, forums)
61
+ 4. Full tier classification with evidence
67
62
 
68
63
  **Output**: Features with tier classification and evidence
69
64
 
70
65
  ---
71
66
 
72
- ### Feature Sequencing
73
-
74
- **Principle**: Order by dependencies within each tier.
75
-
76
- **Common patterns**:
77
- - Create before operate (signup before login)
78
- - Auth before features (login before projects)
79
- - Basic before advanced (CRUD before bulk operations)
80
- - Data before analytics (tracking before dashboards)
81
- - Core before extensions (email before templates)
82
-
83
- **Validation**: No forward dependencies (UC-001 doesn't depend on UC-002)
84
-
85
- **Output**: Sequenced feature list (UC-001, UC-002, UC-003...)
86
-
87
- ---
88
-
89
- ### Use Case Generation
90
-
91
- **Principle**: Lean 80/20 format (~30 lines).
92
-
93
- **Include (20%)**:
94
- - Story (1 line)
95
- - Critical acceptance criteria (3-5 bullets)
96
- - Key business rules (constraints, limits)
97
- - Open questions (blockers)
98
-
99
- **Defer to /dev-specs (80%)**:
100
- - Detailed flows, integrations, edge cases, UI/UX
101
-
102
- **Template**: `templates/use-case.md`
103
-
104
- **Output**: Lean use cases in `brd/use-cases/{feature}/UC-{GROUP}-{NNN}-{slug}.md`
105
-
106
- ---
107
-
108
- ### BRD Structure
109
-
110
- **Project-wide** (`brd/`):
111
- - README.md (all features index)
112
- - context.md (stakeholders, users, constraints)
113
- - references.md (industry, compliance, competitor overview)
114
- - changelog.md
115
-
116
- **Feature-specific** (`features/{feature}/`):
117
- - README.md (feature overview)
118
- - references.md (market research, tier evidence)
119
- - questionnaire-{date}.xlsx
120
-
121
- **Templates**: `templates/brd-references.md`, `templates/feature-references.md`
122
-
123
- **Output**: Organized BRD structure with scope separation
124
-
125
- ---
126
-
127
67
  ### Generate Questionnaire (ALWAYS)
128
68
 
129
69
  **Principle**: Default output. No BRD files created yet.
@@ -163,10 +103,9 @@
163
103
 
164
104
  ### Context Gathering
165
105
 
166
- **Ask 3 questions**:
106
+ **Ask 2 questions**:
167
107
  1. Feature name
168
108
  2. Scope tier (Core/Standard/Full)
169
- 3. Research depth (Quick / Deep)
170
109
 
171
110
  **Duplicate check**: Read `docs-graph.json` if exists, warn if similar feature found
172
111
 
@@ -192,22 +131,70 @@
192
131
 
193
132
  **Mindset**: BRD creation mode. Customer validated research, now create structure.
194
133
 
195
- ### Process
134
+ ### Read Questionnaire
196
135
 
197
136
  **Read questionnaire** (Excel file):
198
137
  - Summary sheet (features, tiers, research)
199
138
  - Questions sheet (customer answers)
200
139
  - References sheet (source URLs)
201
140
 
202
- **Create BRD structure**:
203
- - `brd/` files (README, context, references, changelog)
204
- - `features/{feature}/` folders
205
- - Use cases (lean format, sequenced)
141
+ ---
142
+
143
+ ### Feature Sequencing
144
+
145
+ **Principle**: Order by dependencies within each tier.
206
146
 
207
- **Incorporate answers**:
208
- - Update use cases with customer answers
209
- - Remove questions that were answered
210
- - Keep unanswered questions in "Open Questions"
147
+ **Common patterns**:
148
+ - Create before operate (signup before login)
149
+ - Auth before features (login before projects)
150
+ - Basic before advanced (CRUD before bulk operations)
151
+ - Data before analytics (tracking before dashboards)
152
+ - Core before extensions (email before templates)
153
+
154
+ **Validation**: No forward dependencies (UC-001 doesn't depend on UC-002)
155
+
156
+ **Output**: Sequenced feature list (UC-001, UC-002, UC-003...)
157
+
158
+ ---
159
+
160
+ ### Use Case Generation
161
+
162
+ **Principle**: Lean 80/20 format (~30 lines).
163
+
164
+ **Include (20%)**:
165
+ - Story (1 line)
166
+ - Critical acceptance criteria (3-5 bullets)
167
+ - Key business rules (constraints, limits)
168
+ - Open questions (blockers)
169
+
170
+ **Defer to /dev-specs (80%)**:
171
+ - Detailed flows, integrations, edge cases, UI/UX
172
+
173
+ **Template**: `templates/use-case.md`
174
+
175
+ **Incorporate customer answers**:
176
+ - Update use cases with answers from questionnaire
177
+ - Remove answered questions from "Open Questions"
178
+ - Keep unanswered questions
179
+
180
+ **Output**: Lean use cases in `brd/use-cases/{feature}/UC-{GROUP}-{NNN}-{slug}.md`
181
+
182
+ ---
183
+
184
+ ### BRD Structure Creation
185
+
186
+ **Create project-wide** (`brd/`):
187
+ - README.md (all features index)
188
+ - context.md (stakeholders, users, constraints)
189
+ - references.md (industry, compliance, competitor overview)
190
+ - changelog.md
191
+
192
+ **Create feature-specific** (`features/{feature}/`):
193
+ - README.md (feature overview)
194
+ - references.md (market research, tier evidence from questionnaire)
195
+ - Move questionnaire here if not already
196
+
197
+ **Templates**: `templates/brd-references.md`, `templates/feature-references.md`
211
198
 
212
199
  **Check completeness**:
213
200
  - If gaps remain → note in use cases
@@ -252,9 +239,11 @@
252
239
  - Fresh (ignore questionnaire, do new research)
253
240
 
254
241
  **If reuse**:
255
- - Read Summary sheet (features, tiers, research stats)
256
- - Read References sheet (source URLs)
257
- - Generate BRD structure (no re-research)
242
+ - Execute same process as Process Answers mode
243
+ - Read questionnaire sheets
244
+ - Sequence features
245
+ - Generate use cases
246
+ - Create BRD structure
258
247
 
259
248
  **If fresh**:
260
249
  - Ignore questionnaire