@codihaus/claude-skills 1.6.12 → 1.6.13

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/dev-specs/SKILL.md +19 -13
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@codihaus/claude-skills",
3
- "version": "1.6.12",
3
+ "version": "1.6.13",
4
4
  "description": "Claude Code skills for software development workflow",
5
5
  "main": "src/index.js",
6
6
  "bin": {
package/skills/dev-specs/SKILL.md CHANGED
@@ -125,12 +125,25 @@ Auto-checked and resolved:
125
125
  - `plans/brd/use-cases/{feature}/*.md` - Business requirements
126
126
  - `plans/docs-graph.json` - Dependencies between UCs
127
127
 
128
- ## User Questions
128
+ ## Scope Inference
129
129
 
130
- Ask via `AskUserQuestion`:
131
- 1. **Scope:** Backend only | Frontend only | Full-stack | API/Service | Mobile
132
- 2. **Additional Context:** API specs | DB schema | Design files | Docs
133
- 3. **Testing:** Unit only | Unit + Integration | Unit + Integration + E2E | No tests
130
+ **Analyze UC to determine what's needed** (don't ask user):
131
+
132
+ From UC content, infer:
133
+ - **UI needed?** → UC mentions forms, pages, views, user sees/clicks/enters
134
+ - **API needed?** → UC mentions data operations, persistence, validation
135
+ - **Both?** → Full-stack (most common)
136
+ - **Testing level** → From `_quality-attributes.md` or project standards
137
+
138
+ **Example:**
139
+ - UC: "User can login via email/password form" → Full-stack (form + API + validation)
140
+ - UC: "System sends daily report email" → Backend only (cron job + email service)
141
+ - UC: "User sees loading spinner during API calls" → Frontend only (UI state)
142
+
143
+ **Only ask user for additional context if helpful:**
144
+ - API specs (Swagger, OpenAPI) if integrating external API
145
+ - Design files (Figma) if complex UI
146
+ - DB schema if existing database
134
147
 
135
148
  ## Impact Analysis
136
149
 
@@ -181,13 +194,6 @@ See `references/spec-template.md` for structure.
181
194
  **Focus:** Requirements + acceptance criteria
182
195
  **No:** Pseudocode or detailed HOW
183
196
 
184
- ## Quality Questions
185
-
186
- Ask user for:
187
- 1. **Scope:** Backend only | Frontend only | Full-stack | API/Service | Mobile
188
- 2. **Additional Context:** API specs | DB schema | Design files | Docs
189
- 3. **Testing:** Unit only | Unit + Integration | Unit + Integration + E2E | No tests
190
-
191
197
  ## Tools
192
198
 
193
199
  | Tool | Purpose |
@@ -195,7 +201,7 @@ Ask user for:
195
201
  | `Read` | BRD, tech-context, codebase-context, architecture |
196
202
  | `Glob` | Find related files |
197
203
  | `Write` | Create spec files |
198
- | `AskUserQuestion` | Clarify scope |
204
+ | `AskUserQuestion` | Ask for additional context (API specs, design files) if needed |
199
205
  | `Context7` | Look up API/library patterns |
200
206
 
201
207
  ## Philosophy