bigpowers 2.20.0 → 2.21.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/.pi/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.20.0",
3
+ "version": "2.21.0",
4
4
  "description": "68 skills — 61 agent skills for spec-driven, test-first software development by solo developers",
5
5
  "keywords": [
6
6
  "pi-package"
@@ -37,6 +37,18 @@ See [REFERENCE.md](REFERENCE.md) for the full WSJF scoring rubric.
37
37
 
38
38
  → verify: `grep -c 'wsjf' specs/release-plan.yaml specs/epics/*/epic.yaml`
39
39
 
40
+ ## Conversational Mode
41
+
42
+ If the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.
43
+
44
+ ### 5-Step Flow
45
+
46
+ 1. **Capture**: Parse the natural-language request for what, why, and where. Ask at most 3 clarifying questions before drafting.
47
+ 2. **Locate**: Identify which epic or capability in `specs/epics/` the request affects or replaces.
48
+ 3. **Draft**: Present a structured draft of the proposed story and tasks for user confirmation.
49
+ 4. **Score**: Estimate the WSJF score and explain the calculation so the user understands the priority.
50
+ 5. **Place**: Confirm the final epic placement with the user before writing files.
51
+
40
52
  ## After either mode
41
53
 
42
54
  Run `bash scripts/sync-status-from-epics.sh`. Suggest `plan-work` or `build-epic` for the top-ranked unstarted story.
@@ -39,6 +39,18 @@ See [REFERENCE.md](REFERENCE.md) for the full WSJF scoring rubric.
39
39
 
40
40
  → verify: `grep -c 'wsjf' specs/release-plan.yaml specs/epics/*/epic.yaml`
41
41
 
42
+ ## Conversational Mode
43
+
44
+ If the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.
45
+
46
+ ### 5-Step Flow
47
+
48
+ 1. **Capture**: Parse the natural-language request for what, why, and where. Ask at most 3 clarifying questions before drafting.
49
+ 2. **Locate**: Identify which epic or capability in `specs/epics/` the request affects or replaces.
50
+ 3. **Draft**: Present a structured draft of the proposed story and tasks for user confirmation.
51
+ 4. **Score**: Estimate the WSJF score and explain the calculation so the user understands the priority.
52
+ 5. **Place**: Confirm the final epic placement with the user before writing files.
53
+
42
54
  ## After either mode
43
55
 
44
56
  Run `bash scripts/sync-status-from-epics.sh`. Suggest `plan-work` or `build-epic` for the top-ranked unstarted story.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,10 @@
1
+ # [2.21.0](https://github.com/danielvm-git/bigpowers/compare/v2.20.0...v2.21.0) (2026-06-22)
2
+
3
+
4
+ ### Features
5
+
6
+ * **change-request:** add conversational intake path ([285cecf](https://github.com/danielvm-git/bigpowers/commit/285cecff204273f9333bb6aac6d3c378cb1209b0))
7
+
1
8
  # [2.20.0](https://github.com/danielvm-git/bigpowers/compare/v2.19.0...v2.20.0) (2026-06-21)
2
9
 
3
10
 
package/SKILL-INDEX.md CHANGED
@@ -3,7 +3,7 @@
3
3
  > **DO NOT EDIT** — This file is auto-generated by `scripts/generate-skill-index.sh`.
4
4
  > Edit `SKILL.md` source files or `skills-lock.json` instead. Run `bash scripts/sync-skills.sh` to regenerate.
5
5
 
6
- **Generated:** 2026-06-21T22:00:07Z
6
+ **Generated:** 2026-06-22T01:58:28Z
7
7
  **Skills:** 68
8
8
 
9
9
  ---
@@ -38,6 +38,18 @@ See [REFERENCE.md](REFERENCE.md) for the full WSJF scoring rubric.
38
38
 
39
39
  → verify: `grep -c 'wsjf' specs/release-plan.yaml specs/epics/*/epic.yaml`
40
40
 
41
+ ## Conversational Mode
42
+
43
+ If the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.
44
+
45
+ ### 5-Step Flow
46
+
47
+ 1. **Capture**: Parse the natural-language request for what, why, and where. Ask at most 3 clarifying questions before drafting.
48
+ 2. **Locate**: Identify which epic or capability in `specs/epics/` the request affects or replaces.
49
+ 3. **Draft**: Present a structured draft of the proposed story and tasks for user confirmation.
50
+ 4. **Score**: Estimate the WSJF score and explain the calculation so the user understands the priority.
51
+ 5. **Place**: Confirm the final epic placement with the user before writing files.
52
+
41
53
  ## After either mode
42
54
 
43
55
  Run `bash scripts/sync-status-from-epics.sh`. Suggest `plan-work` or `build-epic` for the top-ranked unstarted story.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.20.0",
3
+ "version": "2.21.0",
4
4
  "description": "61 agent skills for spec-driven, test-first software development by solo developers",
5
5
  "main": "index.js",
6
6
  "scripts": {
package/skills-lock.json CHANGED
@@ -23,7 +23,7 @@
23
23
  },
24
24
  "change-request": {
25
25
  "description": "Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization.",
26
- "sha256": "431cfd2a21ac4515",
26
+ "sha256": "1d1d7a032226b924",
27
27
  "path": "change-request/SKILL.md"
28
28
  },
29
29
  "commit-message": {