bigpowers 2.18.0 → 2.20.0

package/.pi/package.json

@@ -1,7 +1,7 @@
 {
   "name": "bigpowers",
-  "version": "2.18.0",
-  "description": "67 skills — 61 agent skills for spec-driven, test-first software development by solo developers",
+  "version": "2.20.0",
+  "description": "68 skills — 61 agent skills for spec-driven, test-first software development by solo developers",
   "keywords": [
     "pi-package"
   ],

package/.pi/prompts/develop-tdd.md

@@ -30,6 +30,8 @@ If you catch yourself thinking these, stop and reconsider — you are likely dev
 
 ## Workflow
 
+> **Timing:** `bash scripts/bp-timing.sh start develop-tdd` at invocation; `bash scripts/bp-timing.sh end develop-tdd` before handoff.
+
 ### 1. Planning
 
 - [ ] Read active `specs/epics/*/epic.yaml` story tasks or `specs/bugs/BUG-*.md` — understand verify steps

package/.pi/prompts/plan-work.md

@@ -36,6 +36,8 @@ If this plan touches an existing module, run `assess-impact` first to understand
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start plan-work` at invocation; `bash scripts/bp-timing.sh end plan-work` before handoff.
+
 1. **Explore** — Use `Explore` subagent to understand affected modules, existing test patterns, similar prior art, and dependencies.
 
 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/quick-fix.md

@@ -0,0 +1,116 @@
+---
+description: "Streamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger."
+---
+
+
+
+# Quick Fix
+
+Fast-track for trivial data-only fixes that do not require the full bug-fix chain.
+
+When a bug fix is purely data — an add-missing-key, a typo correction, a config value update — the standard 6-skill chain (investigate-bug → diagnose-root → develop-tdd → kickoff-branch → verify-work → release-branch) is wasteful overhead. Quick-fix collapses it to 2 skills: **quick-fix** then **release-branch**.
+
+## Entry Criteria (ALL must be true)
+
+Before invoking quick-fix, evaluate every item in this checklist:
+
+1. **Purely data change** — adding a missing key, fixing a typo, updating a config value, correcting a constant
+2. **No logic change** — no function signature, condition, loop, or control flow is modified
+3. **No refactor risk** — the change does not reorganize or rename existing structures
+4. **No API surface change** — no exported symbol, interface, or contract changes
+5. **Verifiable with a single assertion** — one test, one curl, one grep can prove it works
+6. **Affects ≤ 1 file**
+7. **Affects ≤ 5 lines changed**
+
+## Guardrails (HARD ABORT — all must pass)
+
+If ANY guardrail triggers, **abort immediately** and suggest `investigate-bug` instead:
+
+| Guardrail | Check |
+|-----------|-------|
+| **>1 file** | The fix touches more than one file |
+| **>5 lines** | The diff exceeds 5 lines |
+| **Logic change** | Any function signature, condition, or loop is modified |
+| **Complex verify** | The verify command is more than one pipeline |
+| **Test breakage** | Running `npm test` or equivalent breaks any existing test |
+
+> **Fallback:** If any guardrail triggers, tell the user: *"This fix exceeds quick-fix guardrails. Use `investigate-bug` for the full TDD bug-fix chain instead."*
+
+## Fast-Path Workflow
+
+Only 2 skills needed for eligible fixes:
+
+```
+quick-fix  →  apply change, run one-line verify, commit with fix:
+release-branch  →  merge and ship (existing skill)
+```
+
+**Skipped skills (with justification):**
+
+| Skipped skill | Why skipped |
+|---------------|-------------|
+| `investigate-bug` | Root cause is obvious (data gap, not logic error) |
+| `diagnose-root` | No isolation needed — the data point is the root cause |
+| `develop-tdd` | No logic to test — single assertion proves correctness |
+| `kickoff-branch` | Change is so small it does not warrant a separate worktree |
+
+> Justification is included in the `fix:` commit body so the audit trail is preserved.
+
+## Process
+
+### 1. Evaluate entry criteria
+
+Run the entry criteria checklist above. If any criterion fails → abort, suggest `investigate-bug`.
+
+### 2. Apply the fix
+
+Make the data change — add the missing key, fix the typo, update the value. Keep it to ≤5 lines in 1 file.
+
+### 3. Verify
+
+Run the single-assertion verify command. Example:
+
+```bash
+grep -q "Bosnia" src/flags.js && echo "FIX VERIFIED" || echo "FIX FAILED"
+```
+
+### 4. Commit
+
+```bash
+git add <file>
+git commit -m "fix(<scope>): <description>"
+git commit --amend -m "fix(<scope>): <description>
+
+Skipped skills (justified for data-only change):
+- investigate-bug: root cause is a data gap, not a logic error
+- diagnose-root: the missing data point is the root cause
+- develop-tdd: single assertion proves correctness
+- kickoff-branch: change is too small for a separate worktree"
+```
+
+### 5. Release
+
+Invoke `release-branch` to merge and ship.
+
+## Verify
+
+```bash
+test -f quick-fix/SKILL.md && echo "OK: skill file exists" || echo "FAIL: no skill file"
+grep -q "name: quick-fix" quick-fix/SKILL.md && echo "OK: frontmatter" || echo "FAIL: frontmatter"
+grep -qi "data.only\|trivial\|fast.path\|guardrail\|abort" quick-fix/SKILL.md && echo "OK: entry criteria and guardrails"
+grep -q "quick-fix" SKILL-INDEX.md && echo "OK: in SKILL-INDEX"
+```
+
+## Example
+
+### Bosnia flag missing from FLAGS dictionary
+
+```gherkin
+Given a bug where FLAGS dictionary is missing entry "Bosnia"
+And no logic depends on the missing entry (purely a data gap)
+When the agent invokes quick-fix
+Then the missing entry is added to the dictionary
+And a one-line verify confirms the key exists: grep -q "Bosnia" src/flags.js
+And a fix: commit is created with the skipped-skills rationale in the body
+And the change is ready for release-branch
+```

package/.pi/prompts/release-branch.md

@@ -28,6 +28,8 @@ If unsure and working alone, prefer **solo-local**.
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start release-branch` at invocation; `bash scripts/bp-timing.sh end release-branch` before handoff.
+
 ### 1. Final verification
 
 ```bash

package/.pi/prompts/survey-context.md

@@ -15,6 +15,8 @@ Orchestrate-project 6 phases: Phase 1 Discover - Phase 2 Elaborate - Phase 3 Pla
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start survey-context` at invocation; `bash scripts/bp-timing.sh end survey-context` before handoff.
+
 ### 1. Read CONVENTIONS.md
 
 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

@@ -18,6 +18,8 @@ Review answers "is the code good?"; Verify answers "does the built thing do what
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start verify-work` at invocation; `bash scripts/bp-timing.sh end verify-work` before handoff.
+
 0. **Branch check** — must not be `main`/`master`.
 
 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/develop-tdd/SKILL.md

@@ -32,6 +32,8 @@ If you catch yourself thinking these, stop and reconsider — you are likely dev
 
 ## Workflow
 
+> **Timing:** `bash scripts/bp-timing.sh start develop-tdd` at invocation; `bash scripts/bp-timing.sh end develop-tdd` before handoff.
+
 ### 1. Planning
 
 - [ ] Read active `specs/epics/*/epic.yaml` story tasks or `specs/bugs/BUG-*.md` — understand verify steps

package/.pi/skills/plan-work/SKILL.md

@@ -38,6 +38,8 @@ If this plan touches an existing module, run `assess-impact` first to understand
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start plan-work` at invocation; `bash scripts/bp-timing.sh end plan-work` before handoff.
+
 1. **Explore** — Use `Explore` subagent to understand affected modules, existing test patterns, similar prior art, and dependencies.
 
 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/quick-fix/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: quick-fix
+description: "\"Streamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger.\""
+model: sonnet
+---
+
+
+
+# Quick Fix
+
+Fast-track for trivial data-only fixes that do not require the full bug-fix chain.
+
+When a bug fix is purely data — an add-missing-key, a typo correction, a config value update — the standard 6-skill chain (investigate-bug → diagnose-root → develop-tdd → kickoff-branch → verify-work → release-branch) is wasteful overhead. Quick-fix collapses it to 2 skills: **quick-fix** then **release-branch**.
+
+## Entry Criteria (ALL must be true)
+
+Before invoking quick-fix, evaluate every item in this checklist:
+
+1. **Purely data change** — adding a missing key, fixing a typo, updating a config value, correcting a constant
+2. **No logic change** — no function signature, condition, loop, or control flow is modified
+3. **No refactor risk** — the change does not reorganize or rename existing structures
+4. **No API surface change** — no exported symbol, interface, or contract changes
+5. **Verifiable with a single assertion** — one test, one curl, one grep can prove it works
+6. **Affects ≤ 1 file**
+7. **Affects ≤ 5 lines changed**
+
+## Guardrails (HARD ABORT — all must pass)
+
+If ANY guardrail triggers, **abort immediately** and suggest `investigate-bug` instead:
+
+| Guardrail | Check |
+|-----------|-------|
+| **>1 file** | The fix touches more than one file |
+| **>5 lines** | The diff exceeds 5 lines |
+| **Logic change** | Any function signature, condition, or loop is modified |
+| **Complex verify** | The verify command is more than one pipeline |
+| **Test breakage** | Running `npm test` or equivalent breaks any existing test |
+
+> **Fallback:** If any guardrail triggers, tell the user: *"This fix exceeds quick-fix guardrails. Use `investigate-bug` for the full TDD bug-fix chain instead."*
+
+## Fast-Path Workflow
+
+Only 2 skills needed for eligible fixes:
+
+```
+quick-fix  →  apply change, run one-line verify, commit with fix:
+release-branch  →  merge and ship (existing skill)
+```
+
+**Skipped skills (with justification):**
+
+| Skipped skill | Why skipped |
+|---------------|-------------|
+| `investigate-bug` | Root cause is obvious (data gap, not logic error) |
+| `diagnose-root` | No isolation needed — the data point is the root cause |
+| `develop-tdd` | No logic to test — single assertion proves correctness |
+| `kickoff-branch` | Change is so small it does not warrant a separate worktree |
+
+> Justification is included in the `fix:` commit body so the audit trail is preserved.
+
+## Process
+
+### 1. Evaluate entry criteria
+
+Run the entry criteria checklist above. If any criterion fails → abort, suggest `investigate-bug`.
+
+### 2. Apply the fix
+
+Make the data change — add the missing key, fix the typo, update the value. Keep it to ≤5 lines in 1 file.
+
+### 3. Verify
+
+Run the single-assertion verify command. Example:
+
+```bash
+grep -q "Bosnia" src/flags.js && echo "FIX VERIFIED" || echo "FIX FAILED"
+```
+
+### 4. Commit
+
+```bash
+git add <file>
+git commit -m "fix(<scope>): <description>"
+git commit --amend -m "fix(<scope>): <description>
+
+Skipped skills (justified for data-only change):
+- investigate-bug: root cause is a data gap, not a logic error
+- diagnose-root: the missing data point is the root cause
+- develop-tdd: single assertion proves correctness
+- kickoff-branch: change is too small for a separate worktree"
+```
+
+### 5. Release
+
+Invoke `release-branch` to merge and ship.
+
+## Verify
+
+```bash
+test -f quick-fix/SKILL.md && echo "OK: skill file exists" || echo "FAIL: no skill file"
+grep -q "name: quick-fix" quick-fix/SKILL.md && echo "OK: frontmatter" || echo "FAIL: frontmatter"
+grep -qi "data.only\|trivial\|fast.path\|guardrail\|abort" quick-fix/SKILL.md && echo "OK: entry criteria and guardrails"
+grep -q "quick-fix" SKILL-INDEX.md && echo "OK: in SKILL-INDEX"
+```
+
+## Example
+
+### Bosnia flag missing from FLAGS dictionary
+
+```gherkin
+Given a bug where FLAGS dictionary is missing entry "Bosnia"
+And no logic depends on the missing entry (purely a data gap)
+When the agent invokes quick-fix
+Then the missing entry is added to the dictionary
+And a one-line verify confirms the key exists: grep -q "Bosnia" src/flags.js
+And a fix: commit is created with the skipped-skills rationale in the body
+And the change is ready for release-branch
+```

package/.pi/skills/release-branch/SKILL.md

@@ -30,6 +30,8 @@ If unsure and working alone, prefer **solo-local**.
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start release-branch` at invocation; `bash scripts/bp-timing.sh end release-branch` before handoff.
+
 ### 1. Final verification
 
 ```bash

package/.pi/skills/survey-context/SKILL.md

@@ -17,6 +17,8 @@ Orchestrate-project 6 phases: Phase 1 Discover - Phase 2 Elaborate - Phase 3 Pla
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start survey-context` at invocation; `bash scripts/bp-timing.sh end survey-context` before handoff.
+
 ### 1. Read CONVENTIONS.md
 
 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

@@ -20,6 +20,8 @@ Review answers "is the code good?"; Verify answers "does the built thing do what
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start verify-work` at invocation; `bash scripts/bp-timing.sh end verify-work` before handoff.
+
 0. **Branch check** — must not be `main`/`master`.
 
 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

@@ -1,3 +1,17 @@
+# [2.20.0](https://github.com/danielvm-git/bigpowers/compare/v2.19.0...v2.20.0) (2026-06-21)
+
+
+### Features
+
+* **e18:** quality gates & impact analysis — complete all 5 stories ([e8b06f9](https://github.com/danielvm-git/bigpowers/commit/e8b06f920cd4a71beabf7df96f6ab6e526c57c1f))
+
+# [2.19.0](https://github.com/danielvm-git/bigpowers/compare/v2.18.0...v2.19.0) (2026-06-21)
+
+
+### Features
+
+* **skill:** quick-fix — fast-path for trivial data-only fixes ([77090cb](https://github.com/danielvm-git/bigpowers/commit/77090cb8236c8fc1129773be4391abb67c9401a9))
+
 # [2.18.0](https://github.com/danielvm-git/bigpowers/compare/v2.17.0...v2.18.0) (2026-06-21)
 
 

package/SKILL-INDEX.md

@@ -3,8 +3,8 @@
 > **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:42:28Z
-**Skills:** 67
+**Generated:** 2026-06-21T22:00:07Z
+**Skills:** 68
 
 ---
 
@@ -15,11 +15,11 @@
 | Discover | 6 | `elaborate-spec, map-codebase, research-first, search-skills, survey-context, using-bigpowers` |
 | Design | 7 | `deepen-architecture, define-language, define-success, design-interface, grill-me, grill-with-docs, model-domain` |
 | Plan | 9 | `assess-impact, change-request, plan-refactor, plan-release, plan-work, run-planning, scope-work, seed-conventions, slice-tasks` |
-| Build | 17 | `align-grid, build-epic, craft-skill, deploy, develop-tdd, execute-plan, guard-git, hook-commits, kickoff-branch, orchestrate-project, publish-package, setup-environment, smoke-test, spike-prototype, validate-contracts, wire-ci, wire-observability` |
+| Build | 18 | `align-grid, build-epic, craft-skill, deploy, develop-tdd, execute-plan, guard-git, hook-commits, kickoff-branch, orchestrate-project, publish-package, quick-fix, setup-environment, smoke-test, spike-prototype, validate-contracts, wire-ci, wire-observability` |
 | Verify | 12 | `audit-code, diagnose-root, enforce-first, fix-bug, inspect-quality, investigate-bug, request-review, respond-review, run-evals, trace-requirement, validate-fix, verify-work` |
 | Release | 2 | `commit-message, release-branch` |
 | Sustain | 13 | `compose-workflow, delegate-task, dispatch-agents, edit-document, evolve-skill, migrate-spec, organize-workspace, reset-baseline, session-state, simulate-agents, stocktake-skills, terse-mode, write-document` |
-| **TOTAL** | **66** | |
+| **TOTAL** | **67** | |
 
 ---
 
@@ -60,41 +60,42 @@
 | 31 | Build | `kickoff-branch` | Create a git worktree and feature branch, then verify a clean test baseline befo | ✅ Active |
 | 32 | Build | `orchestrate-project` | Meta-skill that enforces the 6-phase core loop (discover → elaborate → plan  | ✅ Active |
 | 33 | Build | `publish-package` | "Package registry publishing for npm, crates.io, PyPI, and Homebrew. Verifies pr | ✅ Active |
-| 34 | Build | `setup-environment` | Pre-install dependencies and configure tools before development work begins. Use | ✅ Active |
-| 35 | Build | `smoke-test` | "Post-deploy health-check against a live URL. Validates HTTP status, response co | ✅ Active |
-| 36 | Build | `spike-prototype` | Throw-away prototype for unknown problem spaces. Output is learning notes in spe | ✅ Active |
-| 37 | Build | `validate-contracts` | "Assert data shape consistency across system boundaries — live API responses a | ✅ Active |
-| 38 | Build | `wire-ci` | "CI pipeline setup with pre-built templates and local validation. Generates GitH | ✅ Active |
-| 39 | Build | `wire-observability` | Add structured JSON logging, observability commands, and idempotent setup script | ✅ Active |
-| 40 | Verify | `audit-code` | Self-review checklist for the coding agent to run before dispatching a reviewer. | ✅ Active |
-| 41 | Verify | `diagnose-root` | Run 4-phase root cause analysis — reproduce, isolate, hypothesize, verify. Use | ✅ Active |
-| 42 | Verify | `enforce-first` | Apply the F.I.R.S.T test quality rubric (Fast, Independent, Repeatable, Self-Val | ✅ Active |
-| 43 | Verify | `fix-bug` | Bug fix orchestrator — active_flow fix_bug; reads specs/bugs/BUG-*.md; chains  | ✅ Active |
-| 44 | Verify | `inspect-quality` | Interactive QA session where user reports bugs or issues conversationally, and t | ✅ Active |
-| 45 | Verify | `investigate-bug` | Investigate a bug or issue by exploring the codebase to find root cause, then wr | ✅ Active |
-| 46 | Verify | `request-review` | Dispatch a fresh reviewer agent with a clean context to critique the code after  | ✅ Active |
-| 47 | Verify | `respond-review` | Act on a reviewer agent's feedback systematically — categorize findings, apply | ✅ Active |
-| 48 | Verify | `run-evals` | Eval-Driven Development — define capability and regression evals before buildi | ✅ Active |
-| 49 | Verify | `trace-requirement` | Link story IDs from specs/release-plan.yaml + epic capsule directories to the im | ✅ Active |
-| 50 | Verify | `validate-fix` | Prove a fix works before declaring done — re-run the failing test, run the ful | ✅ Active |
-| 51 | Verify | `verify-work` | Multi-phase UAT gate — cold-start smoke, build, typecheck, lint, tests, step-b | ✅ Active |
-| 52 | Release | `commit-message` | Reviews working-tree changes, then drafts a Conventional Commits title/body and  | ✅ Active |
-| 53 | Release | `release-branch` | Make the merge/PR/keep/discard decision for a feature branch, verify coverage ga | ✅ Active |
-| 54 | Sustain | `compose-workflow` | Chain multiple bigpowers skills into a custom workflow recipe saved in specs/. U | ✅ Active |
-| 55 | Sustain | `delegate-task` | Delegate one complex task to a single subagent, review its work in two stages be | ✅ Active |
-| 56 | Sustain | `dispatch-agents` | Dispatch multiple subagents in parallel on independent tasks. No waiting between | ✅ Active |
-| 57 | Sustain | `edit-document` | Edit and improve documents by restructuring sections, improving clarity, and tig | ✅ Active |
-| 58 | Sustain | `evolve-skill` | Benchmark-gated skill evolution — consume bigpowers-benchmark report, propose  | ✅ Active |
-| 59 | Sustain | `migrate-spec` | Detect GSD, spec-kit, or BMAD spec artifacts and transform them into bigpowers Y | ✅ Active |
-| 60 | Sustain | `organize-workspace` | Scans the active workspace for disposable artifacts—logs, caches, stale build  | ✅ Active |
-| 61 | Sustain | `reset-baseline` | Restore the project to a known clean state between agent runs or experiments. Us | ✅ Active |
-| 62 | Sustain | `session-state` | Track implementation decisions and progress in specs/state.yaml to prevent conte | ✅ Active |
-| 63 | Sustain | `simulate-agents` | Run Mock User and Auditor agents against a feature in fresh contexts before huma | ✅ Active |
-| 64 | Sustain | `stocktake-skills` | Sequential subagent batch audit of the bigpowers skill catalog — Quick Scan (c | ✅ Active |
-| 65 | Sustain | `terse-mode` | Fallback ultra-compressed communication mode. Cuts token usage ~75% by dropping  | ✅ Active |
-| 66 | Sustain | `write-document` | Write, organize, and sync high-integrity technical documents using the BMAD meth | ✅ Active |
-
-**Total: 66 active skills.**
+| 34 | Build | `quick-fix` | "Streamlined fast-path for trivial data-only fixes — no TDD, no branching cere | ✅ Active |
+| 35 | Build | `setup-environment` | Pre-install dependencies and configure tools before development work begins. Use | ✅ Active |
+| 36 | Build | `smoke-test` | "Post-deploy health-check against a live URL. Validates HTTP status, response co | ✅ Active |
+| 37 | Build | `spike-prototype` | Throw-away prototype for unknown problem spaces. Output is learning notes in spe | ✅ Active |
+| 38 | Build | `validate-contracts` | "Assert data shape consistency across system boundaries — live API responses a | ✅ Active |
+| 39 | Build | `wire-ci` | "CI pipeline setup with pre-built templates and local validation. Generates GitH | ✅ Active |
+| 40 | Build | `wire-observability` | Add structured JSON logging, observability commands, and idempotent setup script | ✅ Active |
+| 41 | Verify | `audit-code` | Self-review checklist for the coding agent to run before dispatching a reviewer. | ✅ Active |
+| 42 | Verify | `diagnose-root` | Run 4-phase root cause analysis — reproduce, isolate, hypothesize, verify. Use | ✅ Active |
+| 43 | Verify | `enforce-first` | Apply the F.I.R.S.T test quality rubric (Fast, Independent, Repeatable, Self-Val | ✅ Active |
+| 44 | Verify | `fix-bug` | Bug fix orchestrator — active_flow fix_bug; reads specs/bugs/BUG-*.md; chains  | ✅ Active |
+| 45 | Verify | `inspect-quality` | Interactive QA session where user reports bugs or issues conversationally, and t | ✅ Active |
+| 46 | Verify | `investigate-bug` | Investigate a bug or issue by exploring the codebase to find root cause, then wr | ✅ Active |
+| 47 | Verify | `request-review` | Dispatch a fresh reviewer agent with a clean context to critique the code after  | ✅ Active |
+| 48 | Verify | `respond-review` | Act on a reviewer agent's feedback systematically — categorize findings, apply | ✅ Active |
+| 49 | Verify | `run-evals` | Eval-Driven Development — define capability and regression evals before buildi | ✅ Active |
+| 50 | Verify | `trace-requirement` | Link story IDs from specs/release-plan.yaml + epic capsule directories to the im | ✅ Active |
+| 51 | Verify | `validate-fix` | Prove a fix works before declaring done — re-run the failing test, run the ful | ✅ Active |
+| 52 | Verify | `verify-work` | Multi-phase UAT gate — cold-start smoke, build, typecheck, lint, tests, step-b | ✅ Active |
+| 53 | Release | `commit-message` | Reviews working-tree changes, then drafts a Conventional Commits title/body and  | ✅ Active |
+| 54 | Release | `release-branch` | Make the merge/PR/keep/discard decision for a feature branch, verify coverage ga | ✅ Active |
+| 55 | Sustain | `compose-workflow` | Chain multiple bigpowers skills into a custom workflow recipe saved in specs/. U | ✅ Active |
+| 56 | Sustain | `delegate-task` | Delegate one complex task to a single subagent, review its work in two stages be | ✅ Active |
+| 57 | Sustain | `dispatch-agents` | Dispatch multiple subagents in parallel on independent tasks. No waiting between | ✅ Active |
+| 58 | Sustain | `edit-document` | Edit and improve documents by restructuring sections, improving clarity, and tig | ✅ Active |
+| 59 | Sustain | `evolve-skill` | Benchmark-gated skill evolution — consume bigpowers-benchmark report, propose  | ✅ Active |
+| 60 | Sustain | `migrate-spec` | Detect GSD, spec-kit, or BMAD spec artifacts and transform them into bigpowers Y | ✅ Active |
+| 61 | Sustain | `organize-workspace` | Scans the active workspace for disposable artifacts—logs, caches, stale build  | ✅ Active |
+| 62 | Sustain | `reset-baseline` | Restore the project to a known clean state between agent runs or experiments. Us | ✅ Active |
+| 63 | Sustain | `session-state` | Track implementation decisions and progress in specs/state.yaml to prevent conte | ✅ Active |
+| 64 | Sustain | `simulate-agents` | Run Mock User and Auditor agents against a feature in fresh contexts before huma | ✅ Active |
+| 65 | Sustain | `stocktake-skills` | Sequential subagent batch audit of the bigpowers skill catalog — Quick Scan (c | ✅ Active |
+| 66 | Sustain | `terse-mode` | Fallback ultra-compressed communication mode. Cuts token usage ~75% by dropping  | ✅ Active |
+| 67 | Sustain | `write-document` | Write, organize, and sync high-integrity technical documents using the BMAD meth | ✅ Active |
+
+**Total: 67 active skills.**
 
 ---
 

package/develop-tdd/SKILL.md

@@ -31,6 +31,8 @@ If you catch yourself thinking these, stop and reconsider — you are likely dev
 
 ## Workflow
 
+> **Timing:** `bash scripts/bp-timing.sh start develop-tdd` at invocation; `bash scripts/bp-timing.sh end develop-tdd` before handoff.
+
 ### 1. Planning
 
 - [ ] Read active `specs/epics/*/epic.yaml` story tasks or `specs/bugs/BUG-*.md` — understand verify steps

package/package.json

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

package/plan-work/SKILL.md

@@ -37,6 +37,8 @@ If this plan touches an existing module, run `assess-impact` first to understand
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start plan-work` at invocation; `bash scripts/bp-timing.sh end plan-work` before handoff.
+
 1. **Explore** — Use `Explore` subagent to understand affected modules, existing test patterns, similar prior art, and dependencies.
 
 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/quick-fix/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: quick-fix
+description: "Streamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger."
+model: sonnet
+---
+
+
+# Quick Fix
+
+Fast-track for trivial data-only fixes that do not require the full bug-fix chain.
+
+When a bug fix is purely data — an add-missing-key, a typo correction, a config value update — the standard 6-skill chain (investigate-bug → diagnose-root → develop-tdd → kickoff-branch → verify-work → release-branch) is wasteful overhead. Quick-fix collapses it to 2 skills: **quick-fix** then **release-branch**.
+
+## Entry Criteria (ALL must be true)
+
+Before invoking quick-fix, evaluate every item in this checklist:
+
+1. **Purely data change** — adding a missing key, fixing a typo, updating a config value, correcting a constant
+2. **No logic change** — no function signature, condition, loop, or control flow is modified
+3. **No refactor risk** — the change does not reorganize or rename existing structures
+4. **No API surface change** — no exported symbol, interface, or contract changes
+5. **Verifiable with a single assertion** — one test, one curl, one grep can prove it works
+6. **Affects ≤ 1 file**
+7. **Affects ≤ 5 lines changed**
+
+## Guardrails (HARD ABORT — all must pass)
+
+If ANY guardrail triggers, **abort immediately** and suggest `investigate-bug` instead:
+
+| Guardrail | Check |
+|-----------|-------|
+| **>1 file** | The fix touches more than one file |
+| **>5 lines** | The diff exceeds 5 lines |
+| **Logic change** | Any function signature, condition, or loop is modified |
+| **Complex verify** | The verify command is more than one pipeline |
+| **Test breakage** | Running `npm test` or equivalent breaks any existing test |
+
+> **Fallback:** If any guardrail triggers, tell the user: *"This fix exceeds quick-fix guardrails. Use `investigate-bug` for the full TDD bug-fix chain instead."*
+
+## Fast-Path Workflow
+
+Only 2 skills needed for eligible fixes:
+
+```
+quick-fix  →  apply change, run one-line verify, commit with fix:
+release-branch  →  merge and ship (existing skill)
+```
+
+**Skipped skills (with justification):**
+
+| Skipped skill | Why skipped |
+|---------------|-------------|
+| `investigate-bug` | Root cause is obvious (data gap, not logic error) |
+| `diagnose-root` | No isolation needed — the data point is the root cause |
+| `develop-tdd` | No logic to test — single assertion proves correctness |
+| `kickoff-branch` | Change is so small it does not warrant a separate worktree |
+
+> Justification is included in the `fix:` commit body so the audit trail is preserved.
+
+## Process
+
+### 1. Evaluate entry criteria
+
+Run the entry criteria checklist above. If any criterion fails → abort, suggest `investigate-bug`.
+
+### 2. Apply the fix
+
+Make the data change — add the missing key, fix the typo, update the value. Keep it to ≤5 lines in 1 file.
+
+### 3. Verify
+
+Run the single-assertion verify command. Example:
+
+```bash
+grep -q "Bosnia" src/flags.js && echo "FIX VERIFIED" || echo "FIX FAILED"
+```
+
+### 4. Commit
+
+```bash
+git add <file>
+git commit -m "fix(<scope>): <description>"
+git commit --amend -m "fix(<scope>): <description>
+
+Skipped skills (justified for data-only change):
+- investigate-bug: root cause is a data gap, not a logic error
+- diagnose-root: the missing data point is the root cause
+- develop-tdd: single assertion proves correctness
+- kickoff-branch: change is too small for a separate worktree"
+```
+
+### 5. Release
+
+Invoke `release-branch` to merge and ship.
+
+## Verify
+
+```bash
+test -f quick-fix/SKILL.md && echo "OK: skill file exists" || echo "FAIL: no skill file"
+grep -q "name: quick-fix" quick-fix/SKILL.md && echo "OK: frontmatter" || echo "FAIL: frontmatter"
+grep -qi "data.only\|trivial\|fast.path\|guardrail\|abort" quick-fix/SKILL.md && echo "OK: entry criteria and guardrails"
+grep -q "quick-fix" SKILL-INDEX.md && echo "OK: in SKILL-INDEX"
+```
+
+## Example
+
+### Bosnia flag missing from FLAGS dictionary
+
+```gherkin
+Given a bug where FLAGS dictionary is missing entry "Bosnia"
+And no logic depends on the missing entry (purely a data gap)
+When the agent invokes quick-fix
+Then the missing entry is added to the dictionary
+And a one-line verify confirms the key exists: grep -q "Bosnia" src/flags.js
+And a fix: commit is created with the skipped-skills rationale in the body
+And the change is ready for release-branch
+```

package/release-branch/SKILL.md

@@ -29,6 +29,8 @@ If unsure and working alone, prefer **solo-local**.
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start release-branch` at invocation; `bash scripts/bp-timing.sh end release-branch` before handoff.
+
 ### 1. Final verification
 
 ```bash

package/scripts/generate-skill-index.sh

@@ -48,6 +48,7 @@ PHASE_MAP=(
   [build-epic]="Build"
   [spike-prototype]="Build"
   [craft-skill]="Build"
+  [quick-fix]="Build"
   [setup-environment]="Build"
   [wire-observability]="Build"
   [wire-ci]="Build"

package/skills-lock.json

@@ -73,7 +73,7 @@
     },
     "develop-tdd": {
       "description": "Test-driven development with red-green-refactor loop using vertical slices. Use for features (epic tasks) or bugs (specs/bugs/BUG-*.md).",
-      "sha256": "4002d960b18436cd",
+      "sha256": "6ace47f7db4642d4",
       "path": "develop-tdd/SKILL.md"
     },
     "diagnose-root": {
@@ -188,7 +188,7 @@
     },
     "plan-work": {
       "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).\"",
-      "sha256": "12d45efb07a36e94",
+      "sha256": "2e171101c1e24469",
       "path": "plan-work/SKILL.md"
     },
     "publish-package": {
@@ -196,9 +196,14 @@
       "sha256": "25ead1dd4d174d54",
       "path": "publish-package/SKILL.md"
     },
+    "quick-fix": {
+      "description": "\"Streamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger.\"",
+      "sha256": "6b83f22481ff4995",
+      "path": "quick-fix/SKILL.md"
+    },
     "release-branch": {
       "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\".",
-      "sha256": "6b2df2c92230d098",
+      "sha256": "140f4bec3690bd51",
       "path": "release-branch/SKILL.md"
     },
     "request-review": {
@@ -283,7 +288,7 @@
     },
     "survey-context": {
       "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.",
-      "sha256": "891e840a2f292f23",
+      "sha256": "7b68756f984ede71",
       "path": "survey-context/SKILL.md"
     },
     "terse-mode": {
@@ -313,7 +318,7 @@
     },
     "verify-work": {
       "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.",
-      "sha256": "aac80130ca0776ff",
+      "sha256": "a05a1d7ab2a959aa",
       "path": "verify-work/SKILL.md"
     },
     "visual-dashboard": {

package/survey-context/SKILL.md

@@ -16,6 +16,8 @@ Orchestrate-project 6 phases: Phase 1 Discover - Phase 2 Elaborate - Phase 3 Pla
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start survey-context` at invocation; `bash scripts/bp-timing.sh end survey-context` before handoff.
+
 ### 1. Read CONVENTIONS.md
 
 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

@@ -19,6 +19,8 @@ Review answers "is the code good?"; Verify answers "does the built thing do what
 
 ## Process
 
+> **Timing:** `bash scripts/bp-timing.sh start verify-work` at invocation; `bash scripts/bp-timing.sh end verify-work` before handoff.
+
 0. **Branch check** — must not be `main`/`master`.
 
 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).