bigpowers 2.52.0 → 2.53.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 (7) hide show
  1. package/.pi/package.json +1 -1
  2. package/.pi/prompts/build-epic.md +1 -0
  3. package/.pi/skills/build-epic/SKILL.md +1 -0
  4. package/CHANGELOG.md +7 -0
  5. package/package.json +1 -1
  6. package/skills/build-epic/SKILL.md +1 -0
  7. package/skills-lock.json +1 -1
package/.pi/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.52.0",
3
+ "version": "2.53.0",
4
4
  "description": "72 skills — 72 agent skills synthesizing 17 years of software engineering discipline into a prescriptive methodology for solo developers",
5
5
  "keywords": [
6
6
  "pi-package"
package/.pi/prompts/build-epic.md CHANGED
@@ -37,6 +37,7 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
37
37
  6. Run **only the current step** (resume mode) unless user asked for full auto-run.
38
38
  7. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).
39
39
  8. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts/sync-status-from-epics.sh`.
40
+ 9. **Traceability refresh:** Before step 8 (release-branch), run `bash scripts/trace-stories.sh` to regenerate `specs/traceability-matrix.json`, `specs/TRACEABILITY_LATEST.md`, and the `specs/codebase-wiki/` OKF bundle. Surface dark/orphan/stale findings for the just-built epic in your verify summary. If `scripts/trace-stories.sh` is missing or fails, note "trace skipped" and continue — trace failure must be visible, not silent (blocking is gate-trace's job, e38s06).
40
41
 
41
42
  ### Step 6 — audit-code gate (non-optional)
42
43
 
package/.pi/skills/build-epic/SKILL.md CHANGED
@@ -39,6 +39,7 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
39
39
  6. Run **only the current step** (resume mode) unless user asked for full auto-run.
40
40
  7. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).
41
41
  8. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts/sync-status-from-epics.sh`.
42
+ 9. **Traceability refresh:** Before step 8 (release-branch), run `bash scripts/trace-stories.sh` to regenerate `specs/traceability-matrix.json`, `specs/TRACEABILITY_LATEST.md`, and the `specs/codebase-wiki/` OKF bundle. Surface dark/orphan/stale findings for the just-built epic in your verify summary. If `scripts/trace-stories.sh` is missing or fails, note "trace skipped" and continue — trace failure must be visible, not silent (blocking is gate-trace's job, e38s06).
42
43
 
43
44
  ### Step 6 — audit-code gate (non-optional)
44
45
 
package/CHANGELOG.md CHANGED
@@ -1,3 +1,10 @@
1
+ # [2.53.0](https://github.com/danielvm-git/bigpowers/compare/v2.52.0...v2.53.0) (2026-07-03)
2
+
3
+
4
+ ### Features
5
+
6
+ * **e38:** integrate trace-stories.sh into build-epic ([146efa5](https://github.com/danielvm-git/bigpowers/commit/146efa510085cac017f21bfbc6294e87d99a93f5))
7
+
1
8
  # [2.52.0](https://github.com/danielvm-git/bigpowers/compare/v2.51.0...v2.52.0) (2026-07-03)
2
9
 
3
10
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.52.0",
3
+ "version": "2.53.0",
4
4
  "description": "72 agent skills synthesizing 17 years of software engineering discipline into a prescriptive methodology for solo developers",
5
5
  "main": "index.js",
6
6
  "scripts": {
package/skills/build-epic/SKILL.md CHANGED
@@ -39,6 +39,7 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
39
39
  6. Run **only the current step** (resume mode) unless user asked for full auto-run.
40
40
  7. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).
41
41
  8. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts/sync-status-from-epics.sh`.
42
+ 9. **Traceability refresh:** Before step 8 (release-branch), run `bash scripts/trace-stories.sh` to regenerate `specs/traceability-matrix.json`, `specs/TRACEABILITY_LATEST.md`, and the `specs/codebase-wiki/` OKF bundle. Surface dark/orphan/stale findings for the just-built epic in your verify summary. If `scripts/trace-stories.sh` is missing or fails, note "trace skipped" and continue — trace failure must be visible, not silent (blocking is gate-trace's job, e38s06).
42
43
 
43
44
  ### Step 6 — audit-code gate (non-optional)
44
45
 
package/skills-lock.json CHANGED
@@ -23,7 +23,7 @@
23
23
  },
24
24
  "build-epic": {
25
25
  "description": "Eight-step epic build cycle — reads state.yaml, execution-status.yaml, and one epic capsule; updates status via bp-yaml-set or direct edit. Resume mode runs one step per invocation. Use instead of ad-hoc execute-plan for release work.",
26
- "sha256": "e361a976082385fe",
26
+ "sha256": "3d2337356c24ee55",
27
27
  "path": "skills/build-epic/SKILL.md"
28
28
  },
29
29
  "change-request": {