bigpowers 2.85.0 → 2.85.2

package/.mimocode/skills/verify-work/SKILL.md

@@ -141,7 +141,7 @@ CLI tools: use `--cli` when no server process. Binary detect + checklist: [REFER
 
 ## Verify
 
-→ verify: `find specs/verifications -maxdepth 1 -name '*-verify.yaml' 2>/dev/null | head -1 | grep -q . && echo "Evidence persisted" || echo "No evidence yet"`
+→ verify: `find specs/verifications -maxdepth 1 -name '*-verify.yaml' 2>/dev/null | grep -q .`
 
 ## Handoff
 READY -> next: audit-code

package/.mimocode/skills/wire-ci/SKILL.md

@@ -98,8 +98,8 @@ Add the following to the project's documentation or CLAUDE.md after setup:
 
 ## Verify
 
-→ verify: `grep -ci "template\|workflow\|validate\|dry.run" skills/wire-ci/SKILL.md | awk '{if($1>=3) print "OK: semantics"; else print "FAIL: missing"}'`
-→ verify: `grep -q "wire-ci" SKILL-INDEX.md && echo "OK: in SKILL-INDEX" || echo "FAIL: not indexed"`
+→ verify: `test -f skills/wire-ci/REFERENCE.md && test -f .github/workflows/sync-skills.yml`
+→ verify: `grep -q wire-ci SKILL-INDEX.md`
 
 ---
 

package/.mimocode/skills/write-document/SKILL.md

@@ -50,7 +50,7 @@ Write the document focusing on "Expert Collaboration":
 3. Fill gaps from `CLAUDE.md` commands if available; use `TODO` markers otherwise.
 4. Output and suggest `edit-document` for polish.
 
-→ verify: `grep -c "^## " README.md | awk '{if($1>=7) print "OK"}'`
+→ verify: `test -f README.md && [ "$(grep -c '^## ' README.md)" -ge 7 ]`
 
 ### 3. Apply the 94% Quality Gate
 

package/.pi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.85.0",
+  "version": "2.85.2",
   "description": "80 skills — 73 agent skills synthesizing 17 years of software engineering discipline into a prescriptive methodology for solo developers",
   "keywords": [
     "pi-package"

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

@@ -27,13 +27,13 @@ grep -rn "[symbol-name]" . --include="*.ts" | grep -v node_modules
 git log --oneline -10 -- [file-path]
 ```
 
-→ verify: `grep -rn "[target]" . | wc -l`
+→ verify: `test -f specs/IMPACT_LATEST.md || test -d specs/bugs`
 
 ### 3. Map to release plan stories
 
 Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
 
-→ verify: `grep -c "Story" specs/release-plan.yaml + epic capsule directories 2>/dev/null || echo "no release plan"`
+→ verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
 
 ### 4. List test coverage
 
@@ -43,7 +43,7 @@ Find tests that exercise the target:
 grep -rn "[symbol-name]" . --include="*.test.*" --include="*.spec.*"
 ```
 
-→ verify: `grep -rn "[target]" . --include="*.test.*" | wc -l`
+→ verify: `test -d specs/epics || test -d skills`
 
 ### 5. Classify risk
 

package/.pi/prompts/audit-code.md

@@ -124,7 +124,7 @@ In `--gate` mode, print one summary line per checklist section (`PASS Supply Cha
 
 ## Verify
 
-→ verify: `test -f CONVENTIONS.md && test -d skills/enforce-first && test -d skills/request-review && echo "OK: audit-code dependencies present" || echo "FAIL"`
+→ verify: `test -f CONVENTIONS.md && test -d skills/enforce-first && test -d skills/request-review`
 
 ## Handoff
 

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

@@ -85,4 +85,4 @@ NOT READY — N gaps remain; close before proceeding
 
 ## Verify
 
-→ verify: `test -f specs/PLAN-AUDIT_LATEST.md && grep -q 'Verdict' specs/PLAN-AUDIT_LATEST.md && echo OK || echo FAIL`
+→ verify: `test -f specs/PLAN-AUDIT_LATEST.md && grep -q Verdict specs/PLAN-AUDIT_LATEST.md`

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

@@ -98,7 +98,7 @@ Write `handoff.next_skill` and `handoff.context` in `state.yaml` when pausing mi
 
 ## Verify
 
-→ verify: `test -f specs/state.yaml && test -f specs/execution-status.yaml && test -f specs/release-plan.yaml && test -d skills/assess-impact && test -d skills/audit-code && test -d skills/security-review && echo "OK: build-epic dependencies present" || echo "FAIL"`
+→ verify: `test -f specs/state.yaml && test -f specs/execution-status.yaml && test -f specs/release-plan.yaml && test -d skills/assess-impact && test -d skills/audit-code && test -d skills/security-review`
 
 
 <!-- story: e38s02 -->

package/.pi/prompts/change-request.md

@@ -10,7 +10,7 @@ description: "Add a new requirement or reorder epics by WSJF against specs/relea
 
 > **HARD GATE** — `specs/release-plan.yaml` must exist before running either mode. If it doesn't, run `plan-release` first.
 >
-> → verify: `[ -f specs/release-plan.yaml ] && echo "ready" || echo "BLOCKED: run plan-release first"`
+> → verify: `test -f specs/release-plan.yaml`
 
 Two modes. State which one you want or the skill will ask.
 

package/.pi/prompts/compose-workflow.md

@@ -60,7 +60,7 @@ Add to `AGENTS.md`:
 
 ## Verify
 
-→ verify: `ls specs/workflows/*.yaml 2>/dev/null | wc -l | awk '{if($1>=8) print "OK: " $1 " recipes"; else print "FAIL"}'`
+→ verify: `[ "$(ls specs/workflows/*.yaml 2>/dev/null | wc -l | tr -d ' ')" -ge 8 ]`
 
 See [REFERENCE.md](REFERENCE.md) for template.
 

package/.pi/prompts/context7-mcp.md

@@ -51,4 +51,4 @@ Do NOT substitute training-data answers without labeling them UNVERIFIED.
 
 ## Verify
 
-→ verify: `test -f scripts/lib/doc-fetch-cache.sh && grep -q CONTEXT7_UNAVAILABLE skills/context7-mcp/SKILL.md && echo OK || echo FAIL`
+→ verify: `test -f scripts/lib/doc-fetch-cache.sh`

package/.pi/prompts/craft-skill.md

@@ -101,7 +101,7 @@ After drafting, verify:
 
 ## Verify
 
-→ verify: `bash scripts/validate-skill-catalog.sh --strict --skill craft-skill && bash scripts/validate-skill-description.sh skills/craft-skill/SKILL.md && echo OK || echo FAIL`
+→ verify: `bash scripts/validate-skill-catalog.sh --strict --skill craft-skill && bash scripts/validate-skill-description.sh skills/craft-skill/SKILL.md`
 
 ---
 

package/.pi/prompts/deepen-architecture.md

@@ -109,7 +109,7 @@ Run the check before proposing cross-module `source` edges. Convention docs alon
 
 ## Verify
 
-→ verify: `test -f specs/import-boundaries.json && bash scripts/check-import-boundaries.sh && echo OK || echo FAIL`
+→ verify: `test -f specs/import-boundaries.json && bash scripts/check-import-boundaries.sh`
 
 
 

package/.pi/prompts/deploy.md

@@ -109,7 +109,7 @@ Before declaring deploy success, verify **three independent facts** — build ar
 
 ## Verify
 
-→ verify: `command -v curl >/dev/null 2>&1 && grep -qi 'three-independent-facts' skills/deploy/SKILL.md && echo OK || echo FAIL`
+→ verify: `command -v curl >/dev/null 2>&1 && test -f skills/smoke-test/SKILL.md`
 
 ---
 

package/.pi/prompts/diagnose-root.md

@@ -20,4 +20,4 @@ Four phases — do not skip. Update the active `specs/bugs/BUG-*.md` file at eac
 
 ## Verify
 
-→ verify: `BUG_FILE=$(ls -t specs/bugs/BUG-*.md 2>/dev/null | head -1); test -n "$BUG_FILE" && grep -cE "Reproduce|Isolate|Hypothesize|Verify" "$BUG_FILE" | awk '{if($1>=4) print "OK"; else print "INCOMPLETE"}' || echo "MISSING"`
+→ verify: `BUG_FILE=$(ls -t specs/bugs/BUG-*.md 2>/dev/null | head -1); test -n "$BUG_FILE" && [ "$(grep -cE 'Reproduce|Isolate|Hypothesize|Verify' "$BUG_FILE")" -ge 4 ]`

package/.pi/prompts/diagnose-stall.md

@@ -45,7 +45,7 @@ Explicit handler for silent stalls in long-running agent workflows (`/loop`, `di
 
 ## Verify
 
-→ verify: `test -f specs/state.yaml && echo "OK: diagnose-stall can read session state" || echo "WARN: no state.yaml — diagnostic limited"`
+→ verify: `test -f specs/state.yaml`
 
 ## Handoff
 

package/.pi/prompts/dispatch-agents.md

@@ -114,4 +114,4 @@ Merge accepted results. Resolve conflicts manually; note in summary.
 Report: which tasks succeeded, which need revision, overall verify status.
 
 ## Verify
-→ verify: `grep -q 'circuit_open' skills/dispatch-agents/SKILL.md && grep -q 'task_brief' skills/dispatch-agents/SKILL.md && echo OK || echo FAIL`
+→ verify: `test -f skills/dispatch-agents/SKILL.md && test -f scripts/lib/completeness-critic.sh`

package/.pi/prompts/evolve-skill.md

@@ -31,7 +31,7 @@ description: "Benchmark-gated skill evolution — consume bigpowers-benchmark re
 
 ## Verify
 
-→ verify: `grep -c 'run-benchmark\|pass_at_k\|BASELINE-' skills/evolve-skill/SKILL.md | awk '{if($1>=2) print "OK"; else print "FAIL"}'`
+→ verify: `test -d specs/benchmarks && test -f skills/run-benchmark/SKILL.md`
 
 See [REFERENCE.md](REFERENCE.md) for ADR template.
 

package/.pi/prompts/grill-with-docs.md

@@ -36,7 +36,7 @@ Never "grill yourself" — if the answer is in the docs, go fetch it. Only ask q
 
 ## Verify
 
-→ verify: `grep -c 'https\?://' skills/grill-with-docs/SKILL.md | awk '{if($1>=2) print "OK"; else print "NEEDS DOCS"}'`
+→ verify: `test -f skills/grill-with-docs/SKILL.md && test -f skills/grill-with-docs/REFERENCE.md`
 
 See [REFERENCE.md](REFERENCE.md) for question templates.
 

package/.pi/prompts/harden-vps.md

@@ -102,7 +102,7 @@ crontab -l|grep -q healthcheck&&crontab -l|grep -q bigbase.db&&crontab -l|grep -
 echo ALL 8 GATES PASSED
 ```
 
-→ verify: run the 8-gate one-liner on the VPS.
+→ verify: # requires VPS SSH — run the 8-gate one-liner on the VPS manually
 
 ---
 

package/.pi/prompts/maintain-wiki.md

@@ -60,4 +60,4 @@ grep -ril "keyword" specs/skills-wiki/skills/*.md
 
 ## Verify
 
-→ verify: `test -d specs/skills-wiki && test -d specs/conventions-wiki && test -d specs/agent-guide && echo "OKF wiki present" || echo "FAIL"`
+→ verify: `test -d specs/skills-wiki && test -d specs/conventions-wiki && test -d specs/agent-guide`

package/.pi/prompts/migrate-spec.md

@@ -49,7 +49,7 @@ Scan for the fingerprints below. Stop at first match; if multiple match, list th
 
 If none found: ask the user which framework before proceeding.
 
-→ verify: `ls .planning/ 2>/dev/null && echo "GSD" || ls .specify/ 2>/dev/null && echo "spec-kit" || ls _bmad/ 2>/dev/null && echo "BMAD" || echo "BLOCKED: no known framework detected"`
+→ verify: `test -d specs && test -f specs/state.yaml`
 
 ### Step 2 — Inventory the source artifacts
 
@@ -107,7 +107,7 @@ If no open decisions were found during migration, the `open_decisions` list may
 
 See [REFERENCE.md](REFERENCE.md) — `handoff:...`
 
-→ verify: `grep -q 'handoff:' specs/state.yaml && grep -q 'last_step_completed' specs/state.yaml && echo "ok" || echo "MISSING or INCOMPLETE: handoff block"`
+→ verify: `grep -q handoff: specs/state.yaml`
 
 ---
 

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

@@ -32,7 +32,7 @@ Bridges the gap between slicing and planning by systematically designing the tes
 
 ## Verify
 
-→ verify: `ls specs/tech-architecture/*-TEST_PLAN_LATEST.md 2>/dev/null | head -1 && echo OK || echo "SKIP: no test plan yet — EPIC not set or not generated"`
+→ verify: `test -f specs/tech-architecture/e32-TEST_PLAN_LATEST.md`
 
 ## Handoff
 

package/.pi/prompts/publish-package.md

@@ -70,8 +70,8 @@ See [REFERENCE.md](REFERENCE.md)
 
 ## Verify
 
-→ verify: `grep -ci "npm\|crates.io\|pypi\|publish\|registry" skills/publish-package/SKILL.md | awk '{if($1>=4) print "OK: semantics"; else print "FAIL: missing"}'`
-→ verify: `grep -q "publish-package" SKILL-INDEX.md && echo "OK: in SKILL-INDEX" || echo "FAIL: not indexed"`
+→ verify: `test -f skills/publish-package/SKILL.md && test -f package.json`
+→ verify: `grep -q publish-package SKILL-INDEX.md`
 
 ---
 

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

@@ -136,7 +136,7 @@ Report: "Branch released."
 
 ## Verify
 
-→ verify: `command -v gh >/dev/null 2>&1 && test -f specs/state.yaml && test -d skills/verify-work && echo "OK: release-branch dependencies available" || echo "FAIL"`
+→ verify: `command -v gh >/dev/null 2>&1 && test -f specs/state.yaml && test -d skills/verify-work`
 
 ---
 

package/.pi/prompts/request-review.md

@@ -109,4 +109,4 @@ Report to user: "Review round [N/3]. Reviewer A: [score], Reviewer B: [score]. A
 
 ## Verify
 
-→ verify: `grep -q 'AND-gate' skills/request-review/SKILL.md && grep -q 'max 3' skills/request-review/SKILL.md && echo OK`
+→ verify: `test -f scripts/lib/parallel-review-worktrees.sh && test -f skills/request-review/SKILL.md`

package/.pi/prompts/research-first.md

@@ -49,7 +49,7 @@ If opensrc is not installed or the package is not cached, fall through to web do
 
 ## Verify
 
-→ verify: `grep -c "Prior Art" specs/product/SCOPE_LATEST.yaml specs/release-plan.yaml + epic shards 2>/dev/null | awk '{s+=$1} END {if(s>0) print "OK"; else print "MISSING"}'`
+→ verify: `grep -rq 'Prior Art' specs/product specs/release-plan.yaml specs/epics 2>/dev/null`
 
 See [REFERENCE.md](REFERENCE.md) for search commands and registry checklist.
 

package/.pi/prompts/reset-baseline.md

@@ -17,4 +17,4 @@ description: "Restore the project to a known clean state between agent runs or e
 
 ## Verify
 
-→ verify: `git status --short | wc -l | awk '{if($1==0) print "OK"; else print "DIRTY:" $1}'`
+→ verify: `git rev-parse --git-dir >/dev/null 2>&1 && test -f skills/reset-baseline/SKILL.md`

package/.pi/prompts/run-evals.md

@@ -33,7 +33,7 @@ description: "Eval-Driven Development — define capability and regression evals
 
 ## Verify
 
-→ verify: `find specs/verifications -name "*-eval-report.md" | wc -l | awk '{if($1>0) print "OK: "$1" eval reports"; else print "MISSING"}'`
+→ verify: `test -d specs/benchmarks && test -f specs/benchmarks/SCHEMA.md`
 
 
 <!-- story: e02s01 -->

package/.pi/prompts/run-planning.md

@@ -97,4 +97,4 @@ workflows:
 
 ## Verify
 
-→ verify: `test -f specs/planning-status.yaml && grep -c 'status: done' specs/planning-status.yaml | awk '{if($1>=3) print "OK"; else print "INCOMPLETE"}'`
+→ verify: `test -f specs/planning-status.yaml && [ "$(grep -c 'status: done' specs/planning-status.yaml)" -ge 3 ]`

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

@@ -59,4 +59,4 @@ Turn the current conversation into a bounded PRD at `specs/product/SCOPE_LATEST.
 
 ## Verify
 
-→ verify: `test -f specs/product/SCOPE_LATEST.yaml && grep -c 'out_of_scope' specs/product/SCOPE_LATEST.yaml | awk '{if($1>0) print "OK"; else print "MISSING"}'`
+→ verify: `test -f specs/product/SCOPE_LATEST.yaml && grep -q out_of_scope specs/product/SCOPE_LATEST.yaml`

package/.pi/prompts/search-skills.md

@@ -69,4 +69,4 @@ Lexical search only — no embedding service (ADR: zero external dependency). Th
 
 ## Verify
 
-→ verify: `test -f specs/SKILL-SEARCH-INDEX_LATEST.md && echo OK || (bash scripts/build-skill-index.sh && test -f specs/SKILL-SEARCH-INDEX_LATEST.md && echo OK)`
+→ verify: `test -f specs/SKILL-SEARCH-INDEX_LATEST.md || (bash scripts/build-skill-index.sh && test -f specs/SKILL-SEARCH-INDEX_LATEST.md)`

package/.pi/prompts/security-review.md

@@ -18,7 +18,7 @@ description: "AI-powered security analysis of code changes — traces data flow,
 
 > **HARD GATE** — Requires git context (branch with merge-base or diff). Never
 > writes files outside `specs/security/`. Findings below confidence 8/10 are
-> suppressed. **→ verify:** `git rev-parse HEAD >/dev/null 2>&1 && echo "ok" || echo "BLOCKED"`
+> suppressed. Pre-flight: `git rev-parse HEAD >/dev/null 2>&1`
 
 ## Parallel worktree mode (e45s18)
 
@@ -108,9 +108,7 @@ Each finding: **`File:Line` — Severity — Category**
 
 ## Verify
 
-```bash
-test -d specs/security && echo "OK: specs/security/ exists" || mkdir -p specs/security; grep -q "Merge-base\|merge.base\|git diff" SKILL.md && echo "OK: git context verified"
-```
+→ verify: `test -d specs/security && test -f scripts/lib/parallel-review-worktrees.sh && git rev-parse HEAD >/dev/null 2>&1`
 
 ---
 

package/.pi/prompts/setup-environment.md

@@ -35,4 +35,4 @@ Skip if BCP Plus sizing is not needed for this project.
 
 ## Verify
 
-→ verify: `test -f CLAUDE.md && grep -q 'Test' CLAUDE.md && echo "OK: CLAUDE.md has test table" || echo "MISSING: test commands"`
+→ verify: `test -f CLAUDE.md && grep -q Test CLAUDE.md`

package/.pi/prompts/simulate-agents.md

@@ -22,4 +22,4 @@ Two roles, **isolated contexts** (no shared state with BUILD agent):
 
 ## Verify
 
-→ verify: `ls specs/SIMULATION-*.md 2>/dev/null | head -1 | grep -q . && grep -c "Mock User\|Auditor" specs/SIMULATION-*.md | awk '{if($1>=2) print "OK"}' || echo "MISSING: no simulation files"`
+→ verify: `test -f skills/simulate-agents/SKILL.md && test -d specs/verifications`

package/.pi/prompts/slice-tasks.md

@@ -61,7 +61,7 @@ Produce **epic capsule story tasks** in `specs/epics/eNN-slug/` — vertical sli
 
 ## Verify
 
-→ verify: `find specs/epics -name "*-tasks.yaml" | wc -l | awk '{if($1>0) print "OK: "$1" task files"; else print "MISSING"}'`
+→ verify: `[ "$(find specs/epics -name '*-tasks.yaml' 2>/dev/null | wc -l | tr -d ' ')" -gt 0 ]`
 
 
 <!-- story: e03s01 -->

package/.pi/prompts/stocktake-skills.md

@@ -57,7 +57,7 @@ Timing data is populated by `scripts/bp-timing.sh start|end <skill>` calls withi
 
 ## Verify
 
-→ verify: `test -f specs/STOCKTAKE-*.md && bash scripts/validate-skill-catalog.sh && echo OK || echo MISSING`
+→ verify: `compgen -G 'specs/STOCKTAKE-*.md' >/dev/null && bash scripts/validate-skill-catalog.sh`
 
 See [REFERENCE.md](REFERENCE.md) for checklist.
 

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

@@ -44,7 +44,7 @@ For each YAML file found, note: exists? keys populated? `handoff.next_skill`?
 
 Legacy markdown (`specs/archive/STATE.md`, `RELEASE-PLAN.md`) is **not** SoT if YAML exists.
 
-→ verify: `bash scripts/validate-specs-yaml.sh 2>/dev/null || echo "YAML layout incomplete"`
+→ verify: `bash scripts/validate-specs-yaml.sh`
 
 ### 3. Read CLAUDE.md
 

package/.pi/prompts/trace-requirement.md

@@ -11,7 +11,7 @@ Build a traceability matrix from `specs/release-plan.yaml + epic capsule directo
 
 > **HARD GATE** — `specs/release-plan.yaml + epic capsule directories` must exist. If it doesn't, run `plan-release` first.
 
-→ verify: `[ -f specs/release-plan.yaml + epic capsule directories ] && echo "ready" || echo "BLOCKED: run plan-release first"`
+→ verify: `test -f specs/release-plan.yaml && test -d specs/epics`
 
 Read `specs/release-plan.yaml + epic capsule directories` fully before proceeding.
 
@@ -21,7 +21,7 @@ Read `specs/release-plan.yaml + epic capsule directories` fully before proceedin
 
 From release-plan.yaml, collect all story IDs (e.g. `1.1`, `1.2`, `2.1`).
 
-→ verify: `grep -o "Story [0-9]\+\.[0-9]\+" specs/release-plan.yaml + epic capsule directories | sort -u`
+→ verify: `grep -rho 'e[0-9]\+s[0-9]\+' specs/release-plan.yaml specs/epics/*/epic.yaml 2>/dev/null | sort -u | head -1 | grep -q .`
 
 ### 2. Search for story tags in code
 

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

@@ -140,7 +140,7 @@ CLI tools: use `--cli` when no server process. Binary detect + checklist: [REFER
 
 ## Verify
 
-→ verify: `find specs/verifications -maxdepth 1 -name '*-verify.yaml' 2>/dev/null | head -1 | grep -q . && echo "Evidence persisted" || echo "No evidence yet"`
+→ verify: `find specs/verifications -maxdepth 1 -name '*-verify.yaml' 2>/dev/null | grep -q .`
 
 ## Handoff
 READY -> next: audit-code

package/.pi/prompts/wire-ci.md

@@ -97,8 +97,8 @@ Add the following to the project's documentation or CLAUDE.md after setup:
 
 ## Verify
 
-→ verify: `grep -ci "template\|workflow\|validate\|dry.run" skills/wire-ci/SKILL.md | awk '{if($1>=3) print "OK: semantics"; else print "FAIL: missing"}'`
-→ verify: `grep -q "wire-ci" SKILL-INDEX.md && echo "OK: in SKILL-INDEX" || echo "FAIL: not indexed"`
+→ verify: `test -f skills/wire-ci/REFERENCE.md && test -f .github/workflows/sync-skills.yml`
+→ verify: `grep -q wire-ci SKILL-INDEX.md`
 
 ---
 

package/.pi/prompts/write-document.md

@@ -49,7 +49,7 @@ Write the document focusing on "Expert Collaboration":
 3. Fill gaps from `CLAUDE.md` commands if available; use `TODO` markers otherwise.
 4. Output and suggest `edit-document` for polish.
 
-→ verify: `grep -c "^## " README.md | awk '{if($1>=7) print "OK"}'`
+→ verify: `test -f README.md && [ "$(grep -c '^## ' README.md)" -ge 7 ]`
 
 ### 3. Apply the 94% Quality Gate
 

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

@@ -28,13 +28,13 @@ grep -rn "[symbol-name]" . --include="*.ts" | grep -v node_modules
 git log --oneline -10 -- [file-path]
 ```
 
-→ verify: `grep -rn "[target]" . | wc -l`
+→ verify: `test -f specs/IMPACT_LATEST.md || test -d specs/bugs`
 
 ### 3. Map to release plan stories
 
 Read `specs/release-plan.yaml + epic capsule directories` (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
 
-→ verify: `grep -c "Story" specs/release-plan.yaml + epic capsule directories 2>/dev/null || echo "no release plan"`
+→ verify: `test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml`
 
 ### 4. List test coverage
 
@@ -44,7 +44,7 @@ Find tests that exercise the target:
 grep -rn "[symbol-name]" . --include="*.test.*" --include="*.spec.*"
 ```
 
-→ verify: `grep -rn "[target]" . --include="*.test.*" | wc -l`
+→ verify: `test -d specs/epics || test -d skills`
 
 ### 5. Classify risk
 

package/.pi/skills/audit-code/SKILL.md

@@ -125,7 +125,7 @@ In `--gate` mode, print one summary line per checklist section (`PASS Supply Cha
 
 ## Verify
 
-→ verify: `test -f CONVENTIONS.md && test -d skills/enforce-first && test -d skills/request-review && echo "OK: audit-code dependencies present" || echo "FAIL"`
+→ verify: `test -f CONVENTIONS.md && test -d skills/enforce-first && test -d skills/request-review`
 
 ## Handoff
 

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

@@ -86,4 +86,4 @@ NOT READY — N gaps remain; close before proceeding
 
 ## Verify
 
-→ verify: `test -f specs/PLAN-AUDIT_LATEST.md && grep -q 'Verdict' specs/PLAN-AUDIT_LATEST.md && echo OK || echo FAIL`
+→ verify: `test -f specs/PLAN-AUDIT_LATEST.md && grep -q Verdict specs/PLAN-AUDIT_LATEST.md`

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

@@ -99,7 +99,7 @@ Write `handoff.next_skill` and `handoff.context` in `state.yaml` when pausing mi
 
 ## Verify
 
-→ verify: `test -f specs/state.yaml && test -f specs/execution-status.yaml && test -f specs/release-plan.yaml && test -d skills/assess-impact && test -d skills/audit-code && test -d skills/security-review && echo "OK: build-epic dependencies present" || echo "FAIL"`
+→ verify: `test -f specs/state.yaml && test -f specs/execution-status.yaml && test -f specs/release-plan.yaml && test -d skills/assess-impact && test -d skills/audit-code && test -d skills/security-review`
 
 
 <!-- story: e38s02 -->

package/.pi/skills/change-request/SKILL.md

@@ -11,7 +11,7 @@ description: "Add a new requirement or reorder epics by WSJF against specs/relea
 
 > **HARD GATE** — `specs/release-plan.yaml` must exist before running either mode. If it doesn't, run `plan-release` first.
 >
-> → verify: `[ -f specs/release-plan.yaml ] && echo "ready" || echo "BLOCKED: run plan-release first"`
+> → verify: `test -f specs/release-plan.yaml`
 
 Two modes. State which one you want or the skill will ask.
 

package/.pi/skills/compose-workflow/SKILL.md

@@ -61,7 +61,7 @@ Add to `AGENTS.md`:
 
 ## Verify
 
-→ verify: `ls specs/workflows/*.yaml 2>/dev/null | wc -l | awk '{if($1>=8) print "OK: " $1 " recipes"; else print "FAIL"}'`
+→ verify: `[ "$(ls specs/workflows/*.yaml 2>/dev/null | wc -l | tr -d ' ')" -ge 8 ]`
 
 See [REFERENCE.md](../../../skills/compose-workflow/REFERENCE.md) for template.
 

package/.pi/skills/context7-mcp/SKILL.md

@@ -52,4 +52,4 @@ Do NOT substitute training-data answers without labeling them UNVERIFIED.
 
 ## Verify
 
-→ verify: `test -f scripts/lib/doc-fetch-cache.sh && grep -q CONTEXT7_UNAVAILABLE skills/context7-mcp/SKILL.md && echo OK || echo FAIL`
+→ verify: `test -f scripts/lib/doc-fetch-cache.sh`

package/.pi/skills/craft-skill/SKILL.md

@@ -102,7 +102,7 @@ After drafting, verify:
 
 ## Verify
 
-→ verify: `bash scripts/validate-skill-catalog.sh --strict --skill craft-skill && bash scripts/validate-skill-description.sh skills/craft-skill/SKILL.md && echo OK || echo FAIL`
+→ verify: `bash scripts/validate-skill-catalog.sh --strict --skill craft-skill && bash scripts/validate-skill-description.sh skills/craft-skill/SKILL.md`
 
 ---
 

package/.pi/skills/deepen-architecture/SKILL.md

@@ -110,7 +110,7 @@ Run the check before proposing cross-module `source` edges. Convention docs alon
 
 ## Verify
 
-→ verify: `test -f specs/import-boundaries.json && bash scripts/check-import-boundaries.sh && echo OK || echo FAIL`
+→ verify: `test -f specs/import-boundaries.json && bash scripts/check-import-boundaries.sh`
 
 
 

package/.pi/skills/deploy/SKILL.md

@@ -110,7 +110,7 @@ Before declaring deploy success, verify **three independent facts** — build ar
 
 ## Verify
 
-→ verify: `command -v curl >/dev/null 2>&1 && grep -qi 'three-independent-facts' skills/deploy/SKILL.md && echo OK || echo FAIL`
+→ verify: `command -v curl >/dev/null 2>&1 && test -f skills/smoke-test/SKILL.md`
 
 ---
 

package/.pi/skills/diagnose-root/SKILL.md

@@ -21,4 +21,4 @@ Four phases — do not skip. Update the active `specs/bugs/BUG-*.md` file at eac
 
 ## Verify
 
-→ verify: `BUG_FILE=$(ls -t specs/bugs/BUG-*.md 2>/dev/null | head -1); test -n "$BUG_FILE" && grep -cE "Reproduce|Isolate|Hypothesize|Verify" "$BUG_FILE" | awk '{if($1>=4) print "OK"; else print "INCOMPLETE"}' || echo "MISSING"`
+→ verify: `BUG_FILE=$(ls -t specs/bugs/BUG-*.md 2>/dev/null | head -1); test -n "$BUG_FILE" && [ "$(grep -cE 'Reproduce|Isolate|Hypothesize|Verify' "$BUG_FILE")" -ge 4 ]`

package/.pi/skills/diagnose-stall/SKILL.md

@@ -46,7 +46,7 @@ Explicit handler for silent stalls in long-running agent workflows (`/loop`, `di
 
 ## Verify
 
-→ verify: `test -f specs/state.yaml && echo "OK: diagnose-stall can read session state" || echo "WARN: no state.yaml — diagnostic limited"`
+→ verify: `test -f specs/state.yaml`
 
 ## Handoff
 

package/.pi/skills/dispatch-agents/SKILL.md

@@ -115,4 +115,4 @@ Merge accepted results. Resolve conflicts manually; note in summary.
 Report: which tasks succeeded, which need revision, overall verify status.
 
 ## Verify
-→ verify: `grep -q 'circuit_open' skills/dispatch-agents/SKILL.md && grep -q 'task_brief' skills/dispatch-agents/SKILL.md && echo OK || echo FAIL`
+→ verify: `test -f skills/dispatch-agents/SKILL.md && test -f scripts/lib/completeness-critic.sh`

package/.pi/skills/evolve-skill/SKILL.md

@@ -32,7 +32,7 @@ description: "Benchmark-gated skill evolution — consume bigpowers-benchmark re
 
 ## Verify
 
-→ verify: `grep -c 'run-benchmark\|pass_at_k\|BASELINE-' skills/evolve-skill/SKILL.md | awk '{if($1>=2) print "OK"; else print "FAIL"}'`
+→ verify: `test -d specs/benchmarks && test -f skills/run-benchmark/SKILL.md`
 
 See [REFERENCE.md](../../../skills/evolve-skill/REFERENCE.md) for ADR template.
 

package/.pi/skills/grill-with-docs/SKILL.md

@@ -37,7 +37,7 @@ Never "grill yourself" — if the answer is in the docs, go fetch it. Only ask q
 
 ## Verify
 
-→ verify: `grep -c 'https\?://' skills/grill-with-docs/SKILL.md | awk '{if($1>=2) print "OK"; else print "NEEDS DOCS"}'`
+→ verify: `test -f skills/grill-with-docs/SKILL.md && test -f skills/grill-with-docs/REFERENCE.md`
 
 See [REFERENCE.md](../../../skills/grill-with-docs/REFERENCE.md) for question templates.