bigpowers 2.35.0 → 2.36.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.35.0",
3
+ "version": "2.36.0",
4
4
  "description": "71 skills — 70 agent skills for spec-driven, test-first software development by solo developers",
5
5
  "keywords": [
6
6
  "pi-package"
@@ -13,10 +13,11 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
13
13
  >
14
14
  > **HARD GATE** — Not on `main`/`master` before step 3 (kickoff-branch).
15
15
 
16
- ## Eight steps (`epic_cycle` in state.yaml)
16
+ ## Nine steps (`epic_cycle` in state.yaml)
17
17
 
18
18
  | Step | Skill / action |
19
19
  |------|----------------|
20
+ | 0 | `security-review` — threat-model epic scope → `specs/security/epics/<id>/THREAT_MODEL.md` |
20
21
  | 1 | `survey-context` — confirm epic + story |
21
22
  | 2 | `plan-work` — flesh out story `tasks[]` in `specs/epics/eNN-slug/epic.yaml` |
22
23
  | 3 | `kickoff-branch` — feature branch + clean baseline |
@@ -24,17 +25,18 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
24
25
  | 5 | `verify-work` — UAT + mechanical gates |
25
26
  | 6 | `audit-code` — **non-optional gate** (pass/fail; fail → loop back to step 4) |
26
27
  | 7 | `commit-message` — Conventional Commits draft |
27
- | 8 | `release-branch` — PR or solo land (supports `--squash-state`) |
28
+ | 8 | `release-branch` — PR or solo land (supports `--squash-state`) | |
28
29
 
29
30
  ## Process
30
31
 
31
32
  1. Read `specs/state.yaml`, `specs/execution-status.yaml`, `specs/release-plan.yaml`, active `specs/epics/eNN-slug/epic.yaml`.
32
- 2. **Assess Impact (Step 2):** Before writing tasks, run `assess-impact --lightweight` on the proposed change. If the risk score exceeds 7, gate — require a `grill-me` session. Write the impact report to `specs/IMPACT-<epic>-<story>.md`. For net-new code with no existing dependents, skip.
33
- 3. **BCP Tracking (Step 2):** After `plan-work` completes, read the `bcps:` count (Business Complexity Points story size) from the epic capsule and carry it into `state.yaml` as `epic_cycle.story_bcps = N`.
34
- 3. If `epic_cycle.step` missing, set to `1`.
35
- 4. Run **only the current step** (resume mode) unless user asked for full auto-run.
36
- 5. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).
37
- 6. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts/sync-status-from-epics.sh`.
33
+ 2. **Step 0 Threat Model:** Run `security-review` against the epic's scope (read from the epic capsule). Output `specs/security/epics/<epic-id>/THREAT_MODEL.md` with surface area, vulnerability categories, risk level, and mitigation guidance.
34
+ 3. **Assess Impact (Step 2):** Before writing tasks, run `assess-impact --lightweight` on the proposed change. If the risk score exceeds 7, gate require a `grill-me` session. Write the impact report to `specs/IMPACT-<epic>-<story>.md`. For net-new code with no existing dependents, skip.
35
+ 4. **BCP Tracking (Step 2):** After `plan-work` completes, read the `bcps:` count (Business Complexity Points story size) from the epic capsule and carry it into `state.yaml` as `epic_cycle.story_bcps = N`.
36
+ 5. If `epic_cycle.step` missing, set to `1`.
37
+ 6. Run **only the current step** (resume mode) unless user asked for full auto-run.
38
+ 7. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).
39
+ 8. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts/sync-status-from-epics.sh`.
38
40
 
39
41
  ### Step 6 — audit-code gate (non-optional)
40
42
 
@@ -15,10 +15,11 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
15
15
  >
16
16
  > **HARD GATE** — Not on `main`/`master` before step 3 (kickoff-branch).
17
17
 
18
- ## Eight steps (`epic_cycle` in state.yaml)
18
+ ## Nine steps (`epic_cycle` in state.yaml)
19
19
 
20
20
  | Step | Skill / action |
21
21
  |------|----------------|
22
+ | 0 | `security-review` — threat-model epic scope → `specs/security/epics/<id>/THREAT_MODEL.md` |
22
23
  | 1 | `survey-context` — confirm epic + story |
23
24
  | 2 | `plan-work` — flesh out story `tasks[]` in `specs/epics/eNN-slug/epic.yaml` |
24
25
  | 3 | `kickoff-branch` — feature branch + clean baseline |
@@ -26,17 +27,18 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
26
27
  | 5 | `verify-work` — UAT + mechanical gates |
27
28
  | 6 | `audit-code` — **non-optional gate** (pass/fail; fail → loop back to step 4) |
28
29
  | 7 | `commit-message` — Conventional Commits draft |
29
- | 8 | `release-branch` — PR or solo land (supports `--squash-state`) |
30
+ | 8 | `release-branch` — PR or solo land (supports `--squash-state`) | |
30
31
 
31
32
  ## Process
32
33
 
33
34
  1. Read `specs/state.yaml`, `specs/execution-status.yaml`, `specs/release-plan.yaml`, active `specs/epics/eNN-slug/epic.yaml`.
34
- 2. **Assess Impact (Step 2):** Before writing tasks, run `assess-impact --lightweight` on the proposed change. If the risk score exceeds 7, gate — require a `grill-me` session. Write the impact report to `specs/IMPACT-<epic>-<story>.md`. For net-new code with no existing dependents, skip.
35
- 3. **BCP Tracking (Step 2):** After `plan-work` completes, read the `bcps:` count (Business Complexity Points story size) from the epic capsule and carry it into `state.yaml` as `epic_cycle.story_bcps = N`.
36
- 3. If `epic_cycle.step` missing, set to `1`.
37
- 4. Run **only the current step** (resume mode) unless user asked for full auto-run.
38
- 5. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).
39
- 6. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts/sync-status-from-epics.sh`.
35
+ 2. **Step 0 Threat Model:** Run `security-review` against the epic's scope (read from the epic capsule). Output `specs/security/epics/<epic-id>/THREAT_MODEL.md` with surface area, vulnerability categories, risk level, and mitigation guidance.
36
+ 3. **Assess Impact (Step 2):** Before writing tasks, run `assess-impact --lightweight` on the proposed change. If the risk score exceeds 7, gate require a `grill-me` session. Write the impact report to `specs/IMPACT-<epic>-<story>.md`. For net-new code with no existing dependents, skip.
37
+ 4. **BCP Tracking (Step 2):** After `plan-work` completes, read the `bcps:` count (Business Complexity Points story size) from the epic capsule and carry it into `state.yaml` as `epic_cycle.story_bcps = N`.
38
+ 5. If `epic_cycle.step` missing, set to `1`.
39
+ 6. Run **only the current step** (resume mode) unless user asked for full auto-run.
40
+ 7. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).
41
+ 8. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts/sync-status-from-epics.sh`.
40
42
 
41
43
  ### Step 6 — audit-code gate (non-optional)
42
44
 
package/CHANGELOG.md CHANGED
@@ -1,3 +1,10 @@
1
+ # [2.36.0](https://github.com/danielvm-git/bigpowers/compare/v2.35.0...v2.36.0) (2026-06-27)
2
+
3
+
4
+ ### Features
5
+
6
+ * **build-epic:** add Step 0 threat model to epic cycle ([9977f3e](https://github.com/danielvm-git/bigpowers/commit/9977f3e491b9cdefef644e145fa2331fe0ce1154))
7
+
1
8
  # [2.35.0](https://github.com/danielvm-git/bigpowers/compare/v2.34.2...v2.35.0) (2026-06-27)
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-27T16:35:20Z
6
+ **Generated:** 2026-06-27T16:37:32Z
7
7
  **Skills:** 71
8
8
 
9
9
  ---
@@ -14,10 +14,11 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
14
14
  >
15
15
  > **HARD GATE** — Not on `main`/`master` before step 3 (kickoff-branch).
16
16
 
17
- ## Eight steps (`epic_cycle` in state.yaml)
17
+ ## Nine steps (`epic_cycle` in state.yaml)
18
18
 
19
19
  | Step | Skill / action |
20
20
  |------|----------------|
21
+ | 0 | `security-review` — threat-model epic scope → `specs/security/epics/<id>/THREAT_MODEL.md` |
21
22
  | 1 | `survey-context` — confirm epic + story |
22
23
  | 2 | `plan-work` — flesh out story `tasks[]` in `specs/epics/eNN-slug/epic.yaml` |
23
24
  | 3 | `kickoff-branch` — feature branch + clean baseline |
@@ -25,17 +26,18 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
25
26
  | 5 | `verify-work` — UAT + mechanical gates |
26
27
  | 6 | `audit-code` — **non-optional gate** (pass/fail; fail → loop back to step 4) |
27
28
  | 7 | `commit-message` — Conventional Commits draft |
28
- | 8 | `release-branch` — PR or solo land (supports `--squash-state`) |
29
+ | 8 | `release-branch` — PR or solo land (supports `--squash-state`) | |
29
30
 
30
31
  ## Process
31
32
 
32
33
  1. Read `specs/state.yaml`, `specs/execution-status.yaml`, `specs/release-plan.yaml`, active `specs/epics/eNN-slug/epic.yaml`.
33
- 2. **Assess Impact (Step 2):** Before writing tasks, run `assess-impact --lightweight` on the proposed change. If the risk score exceeds 7, gate — require a `grill-me` session. Write the impact report to `specs/IMPACT-<epic>-<story>.md`. For net-new code with no existing dependents, skip.
34
- 3. **BCP Tracking (Step 2):** After `plan-work` completes, read the `bcps:` count (Business Complexity Points story size) from the epic capsule and carry it into `state.yaml` as `epic_cycle.story_bcps = N`.
35
- 3. If `epic_cycle.step` missing, set to `1`.
36
- 4. Run **only the current step** (resume mode) unless user asked for full auto-run.
37
- 5. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).
38
- 6. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts/sync-status-from-epics.sh`.
34
+ 2. **Step 0 Threat Model:** Run `security-review` against the epic's scope (read from the epic capsule). Output `specs/security/epics/<epic-id>/THREAT_MODEL.md` with surface area, vulnerability categories, risk level, and mitigation guidance.
35
+ 3. **Assess Impact (Step 2):** Before writing tasks, run `assess-impact --lightweight` on the proposed change. If the risk score exceeds 7, gate require a `grill-me` session. Write the impact report to `specs/IMPACT-<epic>-<story>.md`. For net-new code with no existing dependents, skip.
36
+ 4. **BCP Tracking (Step 2):** After `plan-work` completes, read the `bcps:` count (Business Complexity Points story size) from the epic capsule and carry it into `state.yaml` as `epic_cycle.story_bcps = N`.
37
+ 5. If `epic_cycle.step` missing, set to `1`.
38
+ 6. Run **only the current step** (resume mode) unless user asked for full auto-run.
39
+ 7. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).
40
+ 8. On story complete, set `execution-status.yaml` story key to `done`; run `bash scripts/sync-status-from-epics.sh`.
39
41
 
40
42
  ### Step 6 — audit-code gate (non-optional)
41
43
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bigpowers",
3
- "version": "2.35.0",
3
+ "version": "2.36.0",
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/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": "7a376ef092fde9cc",
26
+ "sha256": "565d8396889dd9c9",
27
27
  "path": "build-epic/SKILL.md"
28
28
  },
29
29
  "change-request": {