bigpowers 2.19.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.
Files changed (23) hide show
  1. package/.pi/package.json +1 -1
  2. package/.pi/prompts/change-request.md +12 -0
  3. package/.pi/prompts/develop-tdd.md +2 -0
  4. package/.pi/prompts/plan-work.md +2 -0
  5. package/.pi/prompts/release-branch.md +2 -0
  6. package/.pi/prompts/survey-context.md +2 -0
  7. package/.pi/prompts/verify-work.md +2 -0
  8. package/.pi/skills/change-request/SKILL.md +12 -0
  9. package/.pi/skills/develop-tdd/SKILL.md +2 -0
  10. package/.pi/skills/plan-work/SKILL.md +2 -0
  11. package/.pi/skills/release-branch/SKILL.md +2 -0
  12. package/.pi/skills/survey-context/SKILL.md +2 -0
  13. package/.pi/skills/verify-work/SKILL.md +2 -0
  14. package/CHANGELOG.md +14 -0
  15. package/SKILL-INDEX.md +1 -1
  16. package/change-request/SKILL.md +12 -0
  17. package/develop-tdd/SKILL.md +2 -0
  18. package/package.json +1 -1
  19. package/plan-work/SKILL.md +2 -0
  20. package/release-branch/SKILL.md +2 -0
  21. package/skills-lock.json +6 -6
  22. package/survey-context/SKILL.md +2 -0
  23. package/verify-work/SKILL.md +2 -0
package/.pi/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.19.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"
package/.pi/prompts/change-request.md CHANGED
@@ -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.
package/.pi/prompts/develop-tdd.md CHANGED
@@ -30,6 +30,8 @@ If you catch yourself thinking these, stop and reconsider — you are likely dev
30
30
 
31
31
  ## Workflow
32
32
 
33
+ > **Timing:** `bash scripts/bp-timing.sh start develop-tdd` at invocation; `bash scripts/bp-timing.sh end develop-tdd` before handoff.
34
+
33
35
  ### 1. Planning
34
36
 
35
37
  - [ ] Read active `specs/epics/*/epic.yaml` story tasks or `specs/bugs/BUG-*.md` — understand verify steps
package/.pi/prompts/plan-work.md CHANGED
@@ -36,6 +36,8 @@ If this plan touches an existing module, run `assess-impact` first to understand
36
36
 
37
37
  ## Process
38
38
 
39
+ > **Timing:** `bash scripts/bp-timing.sh start plan-work` at invocation; `bash scripts/bp-timing.sh end plan-work` before handoff.
40
+
39
41
  1. **Explore** — Use `Explore` subagent to understand affected modules, existing test patterns, similar prior art, and dependencies.
40
42
 
41
43
  2. **Draft steps** — Break implementation into the smallest possible steps where each step leaves the codebase working, has one observable outcome, and can be verified with a single command. Red-flag check: name any rationalization you caught before moving to step 3.
package/.pi/prompts/release-branch.md CHANGED
@@ -28,6 +28,8 @@ If unsure and working alone, prefer **solo-local**.
28
28
 
29
29
  ## Process
30
30
 
31
+ > **Timing:** `bash scripts/bp-timing.sh start release-branch` at invocation; `bash scripts/bp-timing.sh end release-branch` before handoff.
32
+
31
33
  ### 1. Final verification
32
34
 
33
35
  ```bash
package/.pi/prompts/survey-context.md CHANGED
@@ -15,6 +15,8 @@ Orchestrate-project 6 phases: Phase 1 Discover - Phase 2 Elaborate - Phase 3 Pla
15
15
 
16
16
  ## Process
17
17
 
18
+ > **Timing:** `bash scripts/bp-timing.sh start survey-context` at invocation; `bash scripts/bp-timing.sh end survey-context` before handoff.
19
+
18
20
  ### 1. Read CONVENTIONS.md
19
21
 
20
22
  If `CONVENTIONS.md` exists at the project root, read it first. It contains the rules all agents must follow in this project.
package/.pi/prompts/verify-work.md CHANGED
@@ -18,6 +18,8 @@ Review answers "is the code good?"; Verify answers "does the built thing do what
18
18
 
19
19
  ## Process
20
20
 
21
+ > **Timing:** `bash scripts/bp-timing.sh start verify-work` at invocation; `bash scripts/bp-timing.sh end verify-work` before handoff.
22
+
21
23
  0. **Branch check** — must not be `main`/`master`.
22
24
 
23
25
  1. Read active story tasks from `specs/epics/<capsule>/eNNsYY-tasks.yaml` and story spec from `specs/epics/<capsule>/eNNsYY-<slug>.md` (countable-story-format, Gherkin in §17).
package/.pi/skills/change-request/SKILL.md CHANGED
@@ -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/.pi/skills/develop-tdd/SKILL.md CHANGED
@@ -32,6 +32,8 @@ If you catch yourself thinking these, stop and reconsider — you are likely dev
32
32
 
33
33
  ## Workflow
34
34
 
35
+ > **Timing:** `bash scripts/bp-timing.sh start develop-tdd` at invocation; `bash scripts/bp-timing.sh end develop-tdd` before handoff.
36
+
35
37
  ### 1. Planning
36
38
 
37
39
  - [ ] Read active `specs/epics/*/epic.yaml` story tasks or `specs/bugs/BUG-*.md` — understand verify steps
package/.pi/skills/plan-work/SKILL.md CHANGED
@@ -38,6 +38,8 @@ If this plan touches an existing module, run `assess-impact` first to understand
38
38
 
39
39
  ## Process
40
40
 
41
+ > **Timing:** `bash scripts/bp-timing.sh start plan-work` at invocation; `bash scripts/bp-timing.sh end plan-work` before handoff.
42
+
41
43
  1. **Explore** — Use `Explore` subagent to understand affected modules, existing test patterns, similar prior art, and dependencies.
42
44
 
43
45
  2. **Draft steps** — Break implementation into the smallest possible steps where each step leaves the codebase working, has one observable outcome, and can be verified with a single command. Red-flag check: name any rationalization you caught before moving to step 3.
package/.pi/skills/release-branch/SKILL.md CHANGED
@@ -30,6 +30,8 @@ If unsure and working alone, prefer **solo-local**.
30
30
 
31
31
  ## Process
32
32
 
33
+ > **Timing:** `bash scripts/bp-timing.sh start release-branch` at invocation; `bash scripts/bp-timing.sh end release-branch` before handoff.
34
+
33
35
  ### 1. Final verification
34
36
 
35
37
  ```bash
package/.pi/skills/survey-context/SKILL.md CHANGED
@@ -17,6 +17,8 @@ Orchestrate-project 6 phases: Phase 1 Discover - Phase 2 Elaborate - Phase 3 Pla
17
17
 
18
18
  ## Process
19
19
 
20
+ > **Timing:** `bash scripts/bp-timing.sh start survey-context` at invocation; `bash scripts/bp-timing.sh end survey-context` before handoff.
21
+
20
22
  ### 1. Read CONVENTIONS.md
21
23
 
22
24
  If `CONVENTIONS.md` exists at the project root, read it first. It contains the rules all agents must follow in this project.
package/.pi/skills/verify-work/SKILL.md CHANGED
@@ -20,6 +20,8 @@ Review answers "is the code good?"; Verify answers "does the built thing do what
20
20
 
21
21
  ## Process
22
22
 
23
+ > **Timing:** `bash scripts/bp-timing.sh start verify-work` at invocation; `bash scripts/bp-timing.sh end verify-work` before handoff.
24
+
23
25
  0. **Branch check** — must not be `main`/`master`.
24
26
 
25
27
  1. Read active story tasks from `specs/epics/<capsule>/eNNsYY-tasks.yaml` and story spec from `specs/epics/<capsule>/eNNsYY-<slug>.md` (countable-story-format, Gherkin in §17).
package/CHANGELOG.md CHANGED
@@ -1,3 +1,17 @@
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
+
8
+ # [2.20.0](https://github.com/danielvm-git/bigpowers/compare/v2.19.0...v2.20.0) (2026-06-21)
9
+
10
+
11
+ ### Features
12
+
13
+ * **e18:** quality gates & impact analysis — complete all 5 stories ([e8b06f9](https://github.com/danielvm-git/bigpowers/commit/e8b06f920cd4a71beabf7df96f6ab6e526c57c1f))
14
+
1
15
  # [2.19.0](https://github.com/danielvm-git/bigpowers/compare/v2.18.0...v2.19.0) (2026-06-21)
2
16
 
3
17
 
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-21T21:50:19Z
6
+ **Generated:** 2026-06-22T01:58:28Z
7
7
  **Skills:** 68
8
8
 
9
9
  ---
package/change-request/SKILL.md CHANGED
@@ -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/develop-tdd/SKILL.md CHANGED
@@ -31,6 +31,8 @@ If you catch yourself thinking these, stop and reconsider — you are likely dev
31
31
 
32
32
  ## Workflow
33
33
 
34
+ > **Timing:** `bash scripts/bp-timing.sh start develop-tdd` at invocation; `bash scripts/bp-timing.sh end develop-tdd` before handoff.
35
+
34
36
  ### 1. Planning
35
37
 
36
38
  - [ ] Read active `specs/epics/*/epic.yaml` story tasks or `specs/bugs/BUG-*.md` — understand verify steps
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.19.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/plan-work/SKILL.md CHANGED
@@ -37,6 +37,8 @@ If this plan touches an existing module, run `assess-impact` first to understand
37
37
 
38
38
  ## Process
39
39
 
40
+ > **Timing:** `bash scripts/bp-timing.sh start plan-work` at invocation; `bash scripts/bp-timing.sh end plan-work` before handoff.
41
+
40
42
  1. **Explore** — Use `Explore` subagent to understand affected modules, existing test patterns, similar prior art, and dependencies.
41
43
 
42
44
  2. **Draft steps** — Break implementation into the smallest possible steps where each step leaves the codebase working, has one observable outcome, and can be verified with a single command. Red-flag check: name any rationalization you caught before moving to step 3.
package/release-branch/SKILL.md CHANGED
@@ -29,6 +29,8 @@ If unsure and working alone, prefer **solo-local**.
29
29
 
30
30
  ## Process
31
31
 
32
+ > **Timing:** `bash scripts/bp-timing.sh start release-branch` at invocation; `bash scripts/bp-timing.sh end release-branch` before handoff.
33
+
32
34
  ### 1. Final verification
33
35
 
34
36
  ```bash
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": {
@@ -73,7 +73,7 @@
73
73
  },
74
74
  "develop-tdd": {
75
75
  "description": "Test-driven development with red-green-refactor loop using vertical slices. Use for features (epic tasks) or bugs (specs/bugs/BUG-*.md).",
76
- "sha256": "4002d960b18436cd",
76
+ "sha256": "6ace47f7db4642d4",
77
77
  "path": "develop-tdd/SKILL.md"
78
78
  },
79
79
  "diagnose-root": {
@@ -188,7 +188,7 @@
188
188
  },
189
189
  "plan-work": {
190
190
  "description": "\"PLANNING SPINE STEP 3 of 3 — Plan the work: write detailed implementation tasks into the active epic capsule (specs/epics/eNN-slug/). Produces countable-story-format .md specs and runnable -tasks.yaml files. Use after slice-tasks (step 2). Not a substitute for scope-work (step 1) or slice-tasks (step 2).\"",
191
- "sha256": "12d45efb07a36e94",
191
+ "sha256": "2e171101c1e24469",
192
192
  "path": "plan-work/SKILL.md"
193
193
  },
194
194
  "publish-package": {
@@ -203,7 +203,7 @@
203
203
  },
204
204
  "release-branch": {
205
205
  "description": "Make the merge/PR/keep/discard decision for a feature branch, verify coverage gates, create the PR with gh, and clean up the worktree. Use when a feature is done and ready to ship, or when user says \"release\", \"merge\", or \"open a PR\".",
206
- "sha256": "6b2df2c92230d098",
206
+ "sha256": "140f4bec3690bd51",
207
207
  "path": "release-branch/SKILL.md"
208
208
  },
209
209
  "request-review": {
@@ -288,7 +288,7 @@
288
288
  },
289
289
  "survey-context": {
290
290
  "description": "Per-task context bootstrap — reads existing specs/ and tech-architecture docs to map the current lifecycle phase and suggest the next skill. Use at the start of any task, when returning after a break, or when unsure what to do next. For deriving a tech-stack doc from scratch, use map-codebase first.",
291
- "sha256": "891e840a2f292f23",
291
+ "sha256": "7b68756f984ede71",
292
292
  "path": "survey-context/SKILL.md"
293
293
  },
294
294
  "terse-mode": {
@@ -318,7 +318,7 @@
318
318
  },
319
319
  "verify-work": {
320
320
  "description": "Multi-phase UAT gate — cold-start smoke, build, typecheck, lint, tests, step-by-step manual verification, gaps-closure loop. Use after execute-plan or develop-tdd, before audit-code.",
321
- "sha256": "aac80130ca0776ff",
321
+ "sha256": "a05a1d7ab2a959aa",
322
322
  "path": "verify-work/SKILL.md"
323
323
  },
324
324
  "visual-dashboard": {
package/survey-context/SKILL.md CHANGED
@@ -16,6 +16,8 @@ Orchestrate-project 6 phases: Phase 1 Discover - Phase 2 Elaborate - Phase 3 Pla
16
16
 
17
17
  ## Process
18
18
 
19
+ > **Timing:** `bash scripts/bp-timing.sh start survey-context` at invocation; `bash scripts/bp-timing.sh end survey-context` before handoff.
20
+
19
21
  ### 1. Read CONVENTIONS.md
20
22
 
21
23
  If `CONVENTIONS.md` exists at the project root, read it first. It contains the rules all agents must follow in this project.
package/verify-work/SKILL.md CHANGED
@@ -19,6 +19,8 @@ Review answers "is the code good?"; Verify answers "does the built thing do what
19
19
 
20
20
  ## Process
21
21
 
22
+ > **Timing:** `bash scripts/bp-timing.sh start verify-work` at invocation; `bash scripts/bp-timing.sh end verify-work` before handoff.
23
+
22
24
  0. **Branch check** — must not be `main`/`master`.
23
25
 
24
26
  1. Read active story tasks from `specs/epics/<capsule>/eNNsYY-tasks.yaml` and story spec from `specs/epics/<capsule>/eNNsYY-<slug>.md` (countable-story-format, Gherkin in §17).