bigpowers 2.43.1 → 2.43.2

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 (10) hide show
  1. package/.pi/package.json +1 -1
  2. package/.pi/prompts/plan-release.md +1 -3
  3. package/.pi/skills/plan-release/SKILL.md +1 -3
  4. package/.pi/skills/security-review/SKILL.md +1 -0
  5. package/CHANGELOG.md +7 -0
  6. package/SKILL-INDEX.md +1 -1
  7. package/package.json +1 -1
  8. package/plan-release/SKILL.md +1 -3
  9. package/security-review/SKILL.md +1 -0
  10. package/skills-lock.json +2 -2
package/.pi/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.43.1",
3
+ "version": "2.43.2",
4
4
  "description": "72 skills — 70 agent skills for spec-driven, test-first software development by solo developers",
5
5
  "keywords": [
6
6
  "pi-package"
package/.pi/prompts/plan-release.md CHANGED
@@ -6,7 +6,6 @@ description: "RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/rel
6
6
  # Plan Release
7
7
 
8
8
  > **HARD GATE** — Do NOT run this skill unless `elaborate-spec` has produced a clear spec or the user has already defined the feature in detail. If the problem is still fuzzy, run `elaborate-spec` first.
9
-
10
9
  > **HARD GATE** — `specs/product/SCOPE_LATEST.yaml` (or legacy `specs/product/SCOPE_LATEST.yaml`) must exist. If missing, run `scope-work` first.
11
10
 
12
11
  Synthesize the conversation context into `specs/release-plan.yaml` (index) and shard detail under `specs/epics/`. No new interview — only clarify if something is genuinely ambiguous.
@@ -35,7 +34,7 @@ specs/epics/e01-auth-system/
35
34
  └── e01s02-tasks.yaml # Decoupled task checklist
36
35
  ```
37
36
 
38
- **Rationale:** Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec `.md` from execution `-tasks.yaml` (C1). See `sdd-adequacy-ranking.md` for the full 10-criteria scoring.
37
+ **Rationale:** Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec `.md` from execution `-tasks.yaml` (C1).
39
38
 
40
39
  ## Process
41
40
 
@@ -139,7 +138,6 @@ tasks:
139
138
  ```bash
140
139
  bash scripts/sync-status-from-epics.sh
141
140
  ```
142
-
143
141
  ### 9. Snapshot on planning close (optional)
144
142
 
145
143
  Copy to `specs/product/snapshots/release-<version>/` when the user approves the plan.
package/.pi/skills/plan-release/SKILL.md CHANGED
@@ -8,7 +8,6 @@ model: sonnet
8
8
  # Plan Release
9
9
 
10
10
  > **HARD GATE** — Do NOT run this skill unless `elaborate-spec` has produced a clear spec or the user has already defined the feature in detail. If the problem is still fuzzy, run `elaborate-spec` first.
11
-
12
11
  > **HARD GATE** — `specs/product/SCOPE_LATEST.yaml` (or legacy `specs/product/SCOPE_LATEST.yaml`) must exist. If missing, run `scope-work` first.
13
12
 
14
13
  Synthesize the conversation context into `specs/release-plan.yaml` (index) and shard detail under `specs/epics/`. No new interview — only clarify if something is genuinely ambiguous.
@@ -37,7 +36,7 @@ specs/epics/e01-auth-system/
37
36
  └── e01s02-tasks.yaml # Decoupled task checklist
38
37
  ```
39
38
 
40
- **Rationale:** Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec `.md` from execution `-tasks.yaml` (C1). See `sdd-adequacy-ranking.md` for the full 10-criteria scoring.
39
+ **Rationale:** Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec `.md` from execution `-tasks.yaml` (C1).
41
40
 
42
41
  ## Process
43
42
 
@@ -141,7 +140,6 @@ tasks:
141
140
  ```bash
142
141
  bash scripts/sync-status-from-epics.sh
143
142
  ```
144
-
145
143
  ### 9. Snapshot on planning close (optional)
146
144
 
147
145
  Copy to `specs/product/snapshots/release-<version>/` when the user approves the plan.
package/.pi/skills/security-review/SKILL.md CHANGED
@@ -1,6 +1,7 @@
1
1
  ---
2
2
  name: security-review
3
3
  description: "> AI-powered security analysis of code changes — traces data flow, detects injection, auth bypass, secrets exposure, and unsafe deserialization across files. Use when reviewing pending changes, before release-branch, during verify-work Phase 5, during build-epic Step 0 threat modeling, or when the user says \"security review\" or \"scan for vulns\"."
4
+ model: sonnet
4
5
  ---
5
6
 
6
7
 
package/CHANGELOG.md CHANGED
@@ -1,3 +1,10 @@
1
+ ## [2.43.2](https://github.com/danielvm-git/bigpowers/compare/v2.43.1...v2.43.2) (2026-07-02)
2
+
3
+
4
+ ### Bug Fixes
5
+
6
+ * **ci:** resolve doctrine drift — stale count and line cap ([4930391](https://github.com/danielvm-git/bigpowers/commit/49303917543a56feb6dd47e92641f90bea289cb4))
7
+
1
8
  ## [2.43.1](https://github.com/danielvm-git/bigpowers/compare/v2.43.0...v2.43.1) (2026-07-02)
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-07-02T11:02:02Z
6
+ **Generated:** 2026-07-02T12:07:54Z
7
7
  **Skills:** 72
8
8
 
9
9
  ---
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.43.1",
3
+ "version": "2.43.2",
4
4
  "description": "70 agent skills for spec-driven, test-first software development by solo developers",
5
5
  "main": "index.js",
6
6
  "scripts": {
package/plan-release/SKILL.md CHANGED
@@ -7,7 +7,6 @@ description: "RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/rel
7
7
  # Plan Release
8
8
 
9
9
  > **HARD GATE** — Do NOT run this skill unless `elaborate-spec` has produced a clear spec or the user has already defined the feature in detail. If the problem is still fuzzy, run `elaborate-spec` first.
10
-
11
10
  > **HARD GATE** — `specs/product/SCOPE_LATEST.yaml` (or legacy `specs/product/SCOPE_LATEST.yaml`) must exist. If missing, run `scope-work` first.
12
11
 
13
12
  Synthesize the conversation context into `specs/release-plan.yaml` (index) and shard detail under `specs/epics/`. No new interview — only clarify if something is genuinely ambiguous.
@@ -36,7 +35,7 @@ specs/epics/e01-auth-system/
36
35
  └── e01s02-tasks.yaml # Decoupled task checklist
37
36
  ```
38
37
 
39
- **Rationale:** Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec `.md` from execution `-tasks.yaml` (C1). See `sdd-adequacy-ranking.md` for the full 10-criteria scoring.
38
+ **Rationale:** Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec `.md` from execution `-tasks.yaml` (C1).
40
39
 
41
40
  ## Process
42
41
 
@@ -140,7 +139,6 @@ tasks:
140
139
  ```bash
141
140
  bash scripts/sync-status-from-epics.sh
142
141
  ```
143
-
144
142
  ### 9. Snapshot on planning close (optional)
145
143
 
146
144
  Copy to `specs/product/snapshots/release-<version>/` when the user approves the plan.
package/security-review/SKILL.md CHANGED
@@ -1,5 +1,6 @@
1
1
  ---
2
2
  name: security-review
3
+ model: sonnet
3
4
  description: >
4
5
  AI-powered security analysis of code changes — traces data flow, detects
5
6
  injection, auth bypass, secrets exposure, and unsafe deserialization across
package/skills-lock.json CHANGED
@@ -193,7 +193,7 @@
193
193
  },
194
194
  "plan-release": {
195
195
  "description": "\"RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines. NOT a planning-spine substitute: it does not scope work (scope-work) or write story tasks (plan-work). Use after elaborate-spec when the user wants a versioned release index of epics.\"",
196
- "sha256": "d664fde0d07e88ba",
196
+ "sha256": "6a47658098abc342",
197
197
  "path": "plan-release/SKILL.md"
198
198
  },
199
199
  "plan-work": {
@@ -263,7 +263,7 @@
263
263
  },
264
264
  "security-review": {
265
265
  "description": "> AI-powered security analysis of code changes — traces data flow, detects injection, auth bypass, secrets exposure, and unsafe deserialization across files. Use when reviewing pending changes, before release-branch, during verify-work Phase 5, during build-epic Step 0 threat modeling, or when the user says \"security review\" or \"scan for vulns\".",
266
- "sha256": "24aeeed072282d0c",
266
+ "sha256": "8fe9fa518af2aaa6",
267
267
  "path": "security-review/SKILL.md"
268
268
  },
269
269
  "seed-conventions": {