bigpowers 2.15.0 → 2.17.0

package/.pi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.15.0",
+  "version": "2.17.0",
   "description": "67 skills — 61 agent skills for spec-driven, test-first software development by solo developers",
   "keywords": [
     "pi-package"

package/.pi/prompts/assess-impact.md

@@ -9,6 +9,11 @@ description: Analyze the blast radius of a proposed change before any code is wr
 
 Find the blast radius of the proposed change before a single line is written.
 
+## Modes
+
+- Default: full impact analysis (dependents + affected stories + test coverage mapping)
+- --lightweight: Fast fan-in/fan-out only (<10s). Maps callers and imports without test coverage mapping. Used by build-epic step 2 as a pre-plan gate. Risk score > 7 triggers a mandatory grill-me session before proceeding.
+
 ## Process
 
 ### 1. Identify the target
@@ -74,3 +79,12 @@ grep -rn "[symbol-name]" . --include="*.test.*" --include="*.spec.*"
 → verify: `grep "Risk:" specs/IMPACT.md`
 
 Suggest `plan-work` once risk is understood and any test gaps are noted.
+
+## Risk score gating
+
+In `--lightweight` mode (used by build-epic step 2), assign a numeric risk score (1–10):
+- Fan-in (how many callers): 0–4 points
+- Fan-out (how many dependencies the module itself uses): 0–3 points  
+- Recent churn (git log --oneline -5 count): 0–3 points
+
+**Risk score > 7**: Gate — require a `grill-me` session before proceeding to implementation. Document the grill-me result in the impact report at `specs/IMPACT-<epic>-<story>.md`.

package/.pi/prompts/build-epic.md

@@ -29,7 +29,8 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
 ## Process
 
 1. Read `specs/state.yaml`, `specs/execution-status.yaml`, `specs/release-plan.yaml`, active `specs/epics/eNN-slug/epic.yaml`.
-2. **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`.
+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.
+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`.
 3. If `epic_cycle.step` missing, set to `1`.
 4. Run **only the current step** (resume mode) unless user asked for full auto-run.
 5. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).

package/.pi/prompts/fix-bug.md

@@ -9,15 +9,33 @@ description: Bug fix orchestrator — active_flow fix_bug; reads specs/bugs/BUG-
 
 Orchestrates **fix_bug** flow without mixing epic build state.
 
-> **HARD GATE** — Set `specs/state.yaml` `active_flow: fix_bug`.
+> **HARD GATE** — Set `specs/state.yaml` `active_flow: fix_bug` and `bug_cycle.current_step: 1` before starting.
+
+## Five steps (`bug_cycle` in state.yaml)
+
+| Step | Skill / action |
+|------|----------------|
+| 1 | `investigate-bug` — create BUG-*.md with RCA |
+| 2 | `diagnose-root` — 4-phase root cause analysis |
+| 3 | `develop-tdd` — red-green against bug file verify steps |
+| 4 | `validate-fix` — re-run failing test, full suite, lint |
+| 5 | `release-branch` — PR or solo land the fix |
+
+### Checkpoint / resume
+
+Track progress via `specs/state.yaml` `bug_cycle`:
+- `bug_cycle.current_step`: current step (1–5)
+- `bug_cycle.completed_steps`: completed step numbers
+- `handoff.next_skill`: skill for the current step
+- On resume, read `bug_cycle.current_step` and continue from there
 
 ## Process
 
-1. If no `specs/bugs/BUG-*.md`, run `investigate-bug` first — it handles history check, RCA (via `diagnose-root`), fix approach, and writes the bug file.
-2. `develop-tdd` against the bug file's verify steps.
-3. `validate-fix` — re-run failing test, full suite, lint.
-4. `bash scripts/sync-bugs-registry.sh` — refresh `specs/bugs/registry.yaml`.
-5. Clear `active_flow` or return to `build_epic` when done.
+1. **Step 1 — investigate-bug:** If no `specs/bugs/BUG-*.md`, run `investigate-bug` first — it handles history check, RCA (via `diagnose-root`), fix approach, and writes the bug file. Increment `bug_cycle.current_step` to 2 on completion.
+2. **Step 2 — diagnose-root:** Run 4-phase RCA (reproduce → isolate → hypothesize → verify). Record findings in the bug file. Increment to step 3.
+3. **Step 3 — develop-tdd:** `develop-tdd` against the bug file's verify steps. Increment to step 4 on all-green.
+4. **Step 4 — validate-fix:** `validate-fix` — re-run failing test, full suite, typecheck, lint. Increment to step 5.
+5. **Step 5 — release-branch:** Land the fix via `release-branch`. Clear `bug_cycle` and `active_flow` when done.
 
 ## Bug file SoT
 

package/.pi/prompts/orchestrate-project.md

@@ -31,6 +31,14 @@ claude /orchestrate --mode fast-track
 5. **VERIFY** (1-3 hours): Validate success criteria. Deliverables: UAT evidence, `specs/EVALS-*.md` if used.
 6. **RELEASE** (30 min - 2 hours): Ship to production. Deliverables: Release tag (vX.Y.Z), `state.yaml` `release.last_tag`.
 
+### Checkpoint / resume
+
+Track progress via `specs/state.yaml` `project_cycle`:
+- `project_cycle.current_phase`: current phase (1–6)
+- `project_cycle.completed_phases`: completed phase numbers
+- `handoff.next_skill`: skill for the current phase
+- On resume, read `project_cycle.current_phase` and continue from there
+
 See [REFERENCE.md](REFERENCE.md) for detailed phase specifications and gate types.
 
 ## How Orchestrate Works

package/.pi/prompts/session-state.md

@@ -67,24 +67,23 @@ Whenever a significant decision is made or a milestone is reached:
 
 → verify: `bash scripts/validate-specs-yaml.sh`
 
-## State Write-Lock Protocol
+## Universal checkpoint pattern
 
-> **HARD GATE** — Lock `specs/state.yaml.lock` before writes; stale (>60s) may be force-released.
+Every multi-step flow (>3 steps) in bigpowers uses a cycle counter in `state.yaml`:
 
-1. Check lock exists. If fresh (<60s), wait 2s retry (max 15). Stale → remove.
-2. Write `agent_id: <name>\nacquired_at: <ISO-8601>` to lock.
-3. After write, `rm specs/state.yaml.lock`.
+| Flow | Cycle key | Step field | Phases/Steps |
+|------|-----------|------------|-------------|
+| build-epic | `epic_cycle` | `current_step` | 8 (survey → release) |
+| fix-bug | `bug_cycle` | `current_step` | 5 (investigate → release) |
+| orchestrate-project | `project_cycle` | `current_phase` | 6 (discover → release) |
 
-Lock format:
-```yaml
-agent_id: session-state
-acquired_at: "2026-06-11T14:30:00Z"
-```
+**Checkpoint:** After each step/phase completes, increment the counter in `state.yaml` and update `handoff.next_skill`.
 
+**Resume:** On session start, read the current step/phase from the cycle key — continue from there, not from step 1.
 
-## Operations
+**Completed steps:** Track completed steps in `completed_steps` (comma-separated string) for audit trail.
 
-### show-state (absorbed)
+## Strategic compaction
 
 Print the current session state: `cat specs/state.yaml`, then display `active_flow` and `handoff.next_skill` for quick reference.
 

package/.pi/skills/assess-impact/SKILL.md

@@ -11,6 +11,11 @@ model: sonnet
 
 Find the blast radius of the proposed change before a single line is written.
 
+## Modes
+
+- Default: full impact analysis (dependents + affected stories + test coverage mapping)
+- --lightweight: Fast fan-in/fan-out only (<10s). Maps callers and imports without test coverage mapping. Used by build-epic step 2 as a pre-plan gate. Risk score > 7 triggers a mandatory grill-me session before proceeding.
+
 ## Process
 
 ### 1. Identify the target
@@ -76,3 +81,12 @@ grep -rn "[symbol-name]" . --include="*.test.*" --include="*.spec.*"
 → verify: `grep "Risk:" specs/IMPACT.md`
 
 Suggest `plan-work` once risk is understood and any test gaps are noted.
+
+## Risk score gating
+
+In `--lightweight` mode (used by build-epic step 2), assign a numeric risk score (1–10):
+- Fan-in (how many callers): 0–4 points
+- Fan-out (how many dependencies the module itself uses): 0–3 points  
+- Recent churn (git log --oneline -5 count): 0–3 points
+
+**Risk score > 7**: Gate — require a `grill-me` session before proceeding to implementation. Document the grill-me result in the impact report at `specs/IMPACT-<epic>-<story>.md`.

package/.pi/skills/build-epic/SKILL.md

@@ -31,7 +31,8 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
 ## Process
 
 1. Read `specs/state.yaml`, `specs/execution-status.yaml`, `specs/release-plan.yaml`, active `specs/epics/eNN-slug/epic.yaml`.
-2. **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`.
+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.
+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`.
 3. If `epic_cycle.step` missing, set to `1`.
 4. Run **only the current step** (resume mode) unless user asked for full auto-run.
 5. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).

package/.pi/skills/fix-bug/SKILL.md

@@ -11,15 +11,33 @@ model: sonnet
 
 Orchestrates **fix_bug** flow without mixing epic build state.
 
-> **HARD GATE** — Set `specs/state.yaml` `active_flow: fix_bug`.
+> **HARD GATE** — Set `specs/state.yaml` `active_flow: fix_bug` and `bug_cycle.current_step: 1` before starting.
+
+## Five steps (`bug_cycle` in state.yaml)
+
+| Step | Skill / action |
+|------|----------------|
+| 1 | `investigate-bug` — create BUG-*.md with RCA |
+| 2 | `diagnose-root` — 4-phase root cause analysis |
+| 3 | `develop-tdd` — red-green against bug file verify steps |
+| 4 | `validate-fix` — re-run failing test, full suite, lint |
+| 5 | `release-branch` — PR or solo land the fix |
+
+### Checkpoint / resume
+
+Track progress via `specs/state.yaml` `bug_cycle`:
+- `bug_cycle.current_step`: current step (1–5)
+- `bug_cycle.completed_steps`: completed step numbers
+- `handoff.next_skill`: skill for the current step
+- On resume, read `bug_cycle.current_step` and continue from there
 
 ## Process
 
-1. If no `specs/bugs/BUG-*.md`, run `investigate-bug` first — it handles history check, RCA (via `diagnose-root`), fix approach, and writes the bug file.
-2. `develop-tdd` against the bug file's verify steps.
-3. `validate-fix` — re-run failing test, full suite, lint.
-4. `bash scripts/sync-bugs-registry.sh` — refresh `specs/bugs/registry.yaml`.
-5. Clear `active_flow` or return to `build_epic` when done.
+1. **Step 1 — investigate-bug:** If no `specs/bugs/BUG-*.md`, run `investigate-bug` first — it handles history check, RCA (via `diagnose-root`), fix approach, and writes the bug file. Increment `bug_cycle.current_step` to 2 on completion.
+2. **Step 2 — diagnose-root:** Run 4-phase RCA (reproduce → isolate → hypothesize → verify). Record findings in the bug file. Increment to step 3.
+3. **Step 3 — develop-tdd:** `develop-tdd` against the bug file's verify steps. Increment to step 4 on all-green.
+4. **Step 4 — validate-fix:** `validate-fix` — re-run failing test, full suite, typecheck, lint. Increment to step 5.
+5. **Step 5 — release-branch:** Land the fix via `release-branch`. Clear `bug_cycle` and `active_flow` when done.
 
 ## Bug file SoT
 

package/.pi/skills/orchestrate-project/SKILL.md

@@ -33,6 +33,14 @@ claude /orchestrate --mode fast-track
 5. **VERIFY** (1-3 hours): Validate success criteria. Deliverables: UAT evidence, `specs/EVALS-*.md` if used.
 6. **RELEASE** (30 min - 2 hours): Ship to production. Deliverables: Release tag (vX.Y.Z), `state.yaml` `release.last_tag`.
 
+### Checkpoint / resume
+
+Track progress via `specs/state.yaml` `project_cycle`:
+- `project_cycle.current_phase`: current phase (1–6)
+- `project_cycle.completed_phases`: completed phase numbers
+- `handoff.next_skill`: skill for the current phase
+- On resume, read `project_cycle.current_phase` and continue from there
+
 See [REFERENCE.md](REFERENCE.md) for detailed phase specifications and gate types.
 
 ## How Orchestrate Works

package/.pi/skills/session-state/SKILL.md

@@ -69,24 +69,23 @@ Whenever a significant decision is made or a milestone is reached:
 
 → verify: `bash scripts/validate-specs-yaml.sh`
 
-## State Write-Lock Protocol
+## Universal checkpoint pattern
 
-> **HARD GATE** — Lock `specs/state.yaml.lock` before writes; stale (>60s) may be force-released.
+Every multi-step flow (>3 steps) in bigpowers uses a cycle counter in `state.yaml`:
 
-1. Check lock exists. If fresh (<60s), wait 2s retry (max 15). Stale → remove.
-2. Write `agent_id: <name>\nacquired_at: <ISO-8601>` to lock.
-3. After write, `rm specs/state.yaml.lock`.
+| Flow | Cycle key | Step field | Phases/Steps |
+|------|-----------|------------|-------------|
+| build-epic | `epic_cycle` | `current_step` | 8 (survey → release) |
+| fix-bug | `bug_cycle` | `current_step` | 5 (investigate → release) |
+| orchestrate-project | `project_cycle` | `current_phase` | 6 (discover → release) |
 
-Lock format:
-```yaml
-agent_id: session-state
-acquired_at: "2026-06-11T14:30:00Z"
-```
+**Checkpoint:** After each step/phase completes, increment the counter in `state.yaml` and update `handoff.next_skill`.
 
+**Resume:** On session start, read the current step/phase from the cycle key — continue from there, not from step 1.
 
-## Operations
+**Completed steps:** Track completed steps in `completed_steps` (comma-separated string) for audit trail.
 
-### show-state (absorbed)
+## Strategic compaction
 
 Print the current session state: `cat specs/state.yaml`, then display `active_flow` and `handoff.next_skill` for quick reference.
 

package/CHANGELOG.md

@@ -1,3 +1,17 @@
+# [2.17.0](https://github.com/danielvm-git/bigpowers/compare/v2.16.0...v2.17.0) (2026-06-21)
+
+
+### Features
+
+* **e18s04:** universal checkpoint pattern in fix-bug + orchestrate ([5a47aac](https://github.com/danielvm-git/bigpowers/commit/5a47aac8f0dd1a4463749ab36c64aeded86aa8a4))
+
+# [2.16.0](https://github.com/danielvm-git/bigpowers/compare/v2.15.0...v2.16.0) (2026-06-21)
+
+
+### Features
+
+* **e18s03:** assess-impact --lightweight in build-epic step 2 ([eff1b3a](https://github.com/danielvm-git/bigpowers/commit/eff1b3a3dfa7677db8c525d6424147c08a9b4809))
+
 # [2.15.0](https://github.com/danielvm-git/bigpowers/compare/v2.14.0...v2.15.0) (2026-06-21)
 
 

package/SKILL-INDEX.md

@@ -3,7 +3,7 @@
 > **DO NOT EDIT** — This file is auto-generated by `scripts/generate-skill-index.sh`.
 > Edit `SKILL.md` source files or `skills-lock.json` instead. Run `bash scripts/sync-skills.sh` to regenerate.
 
-**Generated:** 2026-06-21T21:31:53Z
+**Generated:** 2026-06-21T21:41:36Z
 **Skills:** 67
 
 ---

package/assess-impact/SKILL.md

@@ -10,6 +10,11 @@ description: Analyze the blast radius of a proposed change before any code is wr
 
 Find the blast radius of the proposed change before a single line is written.
 
+## Modes
+
+- Default: full impact analysis (dependents + affected stories + test coverage mapping)
+- --lightweight: Fast fan-in/fan-out only (<10s). Maps callers and imports without test coverage mapping. Used by build-epic step 2 as a pre-plan gate. Risk score > 7 triggers a mandatory grill-me session before proceeding.
+
 ## Process
 
 ### 1. Identify the target
@@ -75,3 +80,12 @@ grep -rn "[symbol-name]" . --include="*.test.*" --include="*.spec.*"
 → verify: `grep "Risk:" specs/IMPACT.md`
 
 Suggest `plan-work` once risk is understood and any test gaps are noted.
+
+## Risk score gating
+
+In `--lightweight` mode (used by build-epic step 2), assign a numeric risk score (1–10):
+- Fan-in (how many callers): 0–4 points
+- Fan-out (how many dependencies the module itself uses): 0–3 points  
+- Recent churn (git log --oneline -5 count): 0–3 points
+
+**Risk score > 7**: Gate — require a `grill-me` session before proceeding to implementation. Document the grill-me result in the impact report at `specs/IMPACT-<epic>-<story>.md`.

package/build-epic/SKILL.md

@@ -30,7 +30,8 @@ Orchestrates the **build** flow for a single epic: survey → plan tasks → kic
 ## Process
 
 1. Read `specs/state.yaml`, `specs/execution-status.yaml`, `specs/release-plan.yaml`, active `specs/epics/eNN-slug/epic.yaml`.
-2. **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`.
+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.
+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`.
 3. If `epic_cycle.step` missing, set to `1`.
 4. Run **only the current step** (resume mode) unless user asked for full auto-run.
 5. After step verify passes, increment `epic_cycle.step` in `state.yaml` (or `bash scripts/bp-yaml-set.sh` if available).

package/fix-bug/SKILL.md

@@ -10,15 +10,33 @@ description: Bug fix orchestrator — active_flow fix_bug; reads specs/bugs/BUG-
 
 Orchestrates **fix_bug** flow without mixing epic build state.
 
-> **HARD GATE** — Set `specs/state.yaml` `active_flow: fix_bug`.
+> **HARD GATE** — Set `specs/state.yaml` `active_flow: fix_bug` and `bug_cycle.current_step: 1` before starting.
+
+## Five steps (`bug_cycle` in state.yaml)
+
+| Step | Skill / action |
+|------|----------------|
+| 1 | `investigate-bug` — create BUG-*.md with RCA |
+| 2 | `diagnose-root` — 4-phase root cause analysis |
+| 3 | `develop-tdd` — red-green against bug file verify steps |
+| 4 | `validate-fix` — re-run failing test, full suite, lint |
+| 5 | `release-branch` — PR or solo land the fix |
+
+### Checkpoint / resume
+
+Track progress via `specs/state.yaml` `bug_cycle`:
+- `bug_cycle.current_step`: current step (1–5)
+- `bug_cycle.completed_steps`: completed step numbers
+- `handoff.next_skill`: skill for the current step
+- On resume, read `bug_cycle.current_step` and continue from there
 
 ## Process
 
-1. If no `specs/bugs/BUG-*.md`, run `investigate-bug` first — it handles history check, RCA (via `diagnose-root`), fix approach, and writes the bug file.
-2. `develop-tdd` against the bug file's verify steps.
-3. `validate-fix` — re-run failing test, full suite, lint.
-4. `bash scripts/sync-bugs-registry.sh` — refresh `specs/bugs/registry.yaml`.
-5. Clear `active_flow` or return to `build_epic` when done.
+1. **Step 1 — investigate-bug:** If no `specs/bugs/BUG-*.md`, run `investigate-bug` first — it handles history check, RCA (via `diagnose-root`), fix approach, and writes the bug file. Increment `bug_cycle.current_step` to 2 on completion.
+2. **Step 2 — diagnose-root:** Run 4-phase RCA (reproduce → isolate → hypothesize → verify). Record findings in the bug file. Increment to step 3.
+3. **Step 3 — develop-tdd:** `develop-tdd` against the bug file's verify steps. Increment to step 4 on all-green.
+4. **Step 4 — validate-fix:** `validate-fix` — re-run failing test, full suite, typecheck, lint. Increment to step 5.
+5. **Step 5 — release-branch:** Land the fix via `release-branch`. Clear `bug_cycle` and `active_flow` when done.
 
 ## Bug file SoT
 

package/orchestrate-project/SKILL.md

@@ -32,6 +32,14 @@ claude /orchestrate --mode fast-track
 5. **VERIFY** (1-3 hours): Validate success criteria. Deliverables: UAT evidence, `specs/EVALS-*.md` if used.
 6. **RELEASE** (30 min - 2 hours): Ship to production. Deliverables: Release tag (vX.Y.Z), `state.yaml` `release.last_tag`.
 
+### Checkpoint / resume
+
+Track progress via `specs/state.yaml` `project_cycle`:
+- `project_cycle.current_phase`: current phase (1–6)
+- `project_cycle.completed_phases`: completed phase numbers
+- `handoff.next_skill`: skill for the current phase
+- On resume, read `project_cycle.current_phase` and continue from there
+
 See [REFERENCE.md](REFERENCE.md) for detailed phase specifications and gate types.
 
 ## How Orchestrate Works

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.15.0",
+  "version": "2.17.0",
   "description": "61 agent skills for spec-driven, test-first software development by solo developers",
   "main": "index.js",
   "scripts": {

package/session-state/SKILL.md

@@ -68,24 +68,23 @@ Whenever a significant decision is made or a milestone is reached:
 
 → verify: `bash scripts/validate-specs-yaml.sh`
 
-## State Write-Lock Protocol
+## Universal checkpoint pattern
 
-> **HARD GATE** — Lock `specs/state.yaml.lock` before writes; stale (>60s) may be force-released.
+Every multi-step flow (>3 steps) in bigpowers uses a cycle counter in `state.yaml`:
 
-1. Check lock exists. If fresh (<60s), wait 2s retry (max 15). Stale → remove.
-2. Write `agent_id: <name>\nacquired_at: <ISO-8601>` to lock.
-3. After write, `rm specs/state.yaml.lock`.
+| Flow | Cycle key | Step field | Phases/Steps |
+|------|-----------|------------|-------------|
+| build-epic | `epic_cycle` | `current_step` | 8 (survey → release) |
+| fix-bug | `bug_cycle` | `current_step` | 5 (investigate → release) |
+| orchestrate-project | `project_cycle` | `current_phase` | 6 (discover → release) |
 
-Lock format:
-```yaml
-agent_id: session-state
-acquired_at: "2026-06-11T14:30:00Z"
-```
+**Checkpoint:** After each step/phase completes, increment the counter in `state.yaml` and update `handoff.next_skill`.
 
+**Resume:** On session start, read the current step/phase from the cycle key — continue from there, not from step 1.
 
-## Operations
+**Completed steps:** Track completed steps in `completed_steps` (comma-separated string) for audit trail.
 
-### show-state (absorbed)
+## Strategic compaction
 
 Print the current session state: `cat specs/state.yaml`, then display `active_flow` and `handoff.next_skill` for quick reference.
 

package/skills-lock.json

@@ -8,7 +8,7 @@
     },
     "assess-impact": {
       "description": "Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks \"what does this break?\".",
-      "sha256": "cad0c4534f31a207",
+      "sha256": "740925970c6cf9ce",
       "path": "assess-impact/SKILL.md"
     },
     "audit-code": {
@@ -18,7 +18,7 @@
     },
     "build-epic": {
       "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.",
-      "sha256": "d33ba1c86463d91f",
+      "sha256": "3c1707cca32b24de",
       "path": "build-epic/SKILL.md"
     },
     "change-request": {
@@ -113,7 +113,7 @@
     },
     "fix-bug": {
       "description": "Bug fix orchestrator — active_flow fix_bug; reads specs/bugs/BUG-*.md; chains investigate-bug, develop-tdd, validate-fix. Use when user reports a defect.",
-      "sha256": "466c0847b5312b6f",
+      "sha256": "aa6fe406ba87a648",
       "path": "fix-bug/SKILL.md"
     },
     "grill-me": {
@@ -168,7 +168,7 @@
     },
     "orchestrate-project": {
       "description": "Meta-skill that enforces the 6-phase core loop (discover → elaborate → plan → build → verify → release) with hard gates. Use to coordinate multi-phase projects with guaranteed quality checkpoints. One-time command for the entire project lifecycle.",
-      "sha256": "aef26df7a83a4cd3",
+      "sha256": "542276f88198ae72",
       "path": "orchestrate-project/SKILL.md"
     },
     "organize-workspace": {
@@ -248,7 +248,7 @@
     },
     "session-state": {
       "description": "Track implementation decisions and progress in specs/state.yaml to prevent context rot. Use at the start of a session to load context, and whenever a significant decision is made or a milestone is reached.",
-      "sha256": "5ac473ace06c72b1",
+      "sha256": "4efd54a453e3e2cd",
       "path": "session-state/SKILL.md"
     },
     "setup-environment": {