bigpowers 2.19.0 → 2.20.0

package/.pi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.19.0",
+  "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/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/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,10 @@
+# [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)
 
 

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:50:19Z
+**Generated:** 2026-06-21T22:00:07Z
 **Skills:** 68
 
 ---

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.19.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/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/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": {
@@ -203,7 +203,7 @@
     },
     "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": {
@@ -288,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": {
@@ -318,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).