bigpowers 2.84.1 → 2.85.1

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

@@ -5,7 +5,7 @@ description: "Create new bigpowers skills with proper structure, progressive dis
 
 # Craft Skill
 
-> **HARD GATE** — Do NOT name a skill without a two-word verb-noun pair. Do NOT merge a new skill without running `sync-skills.sh` — the generated `.cursor/rules/` and `.gemini/` artifacts must match the source SKILL.md.
+> **HARD GATE** — Do NOT name a skill without a two-word verb-noun pair. Do NOT merge a new skill without running `sync-skills.sh`. Generated `.cursor/rules/` and `.gemini/` artifacts MUST match the source SKILL.md.
 
 ## CSO Description Discipline (e45s02)
 
@@ -20,11 +20,25 @@ The YAML `description` is the **Catalog Selection Object** — the only field ag
 
 Move process detail into the SKILL.md body or REFERENCE.md — never into `description`.
 
+## Agentic STE body discipline (e79s02)
+
+Skill-body instructional prose MUST follow [AGENTIC-STE.md](../../docs/AGENTIC-STE.md).
+
+| Rule | Limit |
+|------|-------|
+| Sentence length | ≤20 words per instruction sentence |
+| Voice | Imperative, active |
+| Directive terms | MUST, MUST NOT, NEVER, ALWAYS, DO, DO NOT |
+| Banned modals | should, might, could, may, consider, try, generally, typically |
+| Scope | SKILL.md body only — not YAML `description`, not `terse-mode` output |
+
+> **HARD GATE** — Do NOT merge a new or edited skill until `bash scripts/validate-agentic-ste.sh --strict skills/<name>/SKILL.md` exits 0. Fix violations before `sync-skills.sh`.
+
 ## Process
 
 1. **Gather requirements** — ask user about:
    - What task/domain does the skill cover?
-   - What specific use cases should it handle?
+   - Which use cases must the skill handle?
    - Does it need executable scripts or just instructions?
    - Any reference materials to include?
    - What specs/ output does it produce (if any)?
@@ -40,7 +54,8 @@ Move process detail into the SKILL.md body or REFERENCE.md — never into `descr
    - Additional reference files if content exceeds 100 lines
    - Utility scripts if deterministic operations needed
 
-   **Auto-skill from library README:** When user provides a library README or API docs URL, extract: triggers, HARD GATEs, verify commands, specs/ output — draft SKILL.md without inventing APIs not in the source.
+   **Auto-skill from library README:** When user provides a library README or API docs URL, extract triggers and HARD GATEs.
+   Draft verify commands and specs/ output into SKILL.md. Do NOT invent APIs not in the source.
 
 4. Add `model:` frontmatter (`haiku` | `sonnet` | `opus`) per [model-profiles.md](https://github.com/danielvm-git/bigpowers/blob/main/docs/references/model-profiles.md).
 
@@ -49,10 +64,11 @@ Move process detail into the SKILL.md body or REFERENCE.md — never into `descr
 5. **Review with user** — present draft and ask:
    - Does this cover your use cases?
    - Anything missing or unclear?
-   - Should any section be more/less detailed?
+   - Does any section need more or less detail?
 
 6. **Completion-honesty gate (HARD GATE — e45s02)** — Before declaring done:
    - Run `bash scripts/validate-skill-description.sh skills/<name>/SKILL.md` — must exit 0
+   - Run `bash scripts/validate-agentic-ste.sh --strict skills/<name>/SKILL.md` — must exit 0 (e79s02)
    - Run `bash scripts/sync-skills.sh` — must complete without error
    - Run `bash scripts/run-skill-verify.sh <name>` if the skill defines a verify command
    - Show terminal output for each — narration without evidence is rejected
@@ -77,6 +93,7 @@ After drafting, verify:
 - [ ] Consistent terminology with CONVENTIONS.md
 - [ ] specs/ output documented if applicable
 - [ ] `validate-skill-description.sh` exits 0
+- [ ] `validate-agentic-ste.sh --strict` exits 0 (e79s02)
 - [ ] `sync-skills.sh` run to propagate to Cursor/Gemini
 - [ ] `bash scripts/validate-skill-catalog.sh` passes for the new skill (HARD GATE — completion honesty)
 
@@ -84,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/seed-conventions.md

@@ -8,6 +8,7 @@ description: "Generate CLAUDE.md and CONVENTIONS.md for a brand-new project thro
 # story: e10s02
 # story: e51s02
 # story: e45s21
+# story: e79s03
 
 
 # Seed Conventions
@@ -31,13 +32,25 @@ Ask the user these questions (one at a time, wait for each answer):
 2. **Stack** — "What language, framework, and runtime? (e.g. TypeScript / Next.js / Node 22)"
 2b. **Stack profile (optional)** — Offer: `swift`, `typescript-vue`, `node-service`, or none. If chosen, merge the matching fragment from `profiles/<name>.md` into generated `CONVENTIONS.md`.
 3. **Commands** — "What commands do you use for: run, test, build, lint?"
-3b. **Preflight (optional)** — "What single command runs your full local green stack (test + lint + build)? If you don't have one, we'll chain your Test + Lint + Build answers into a **Preflight** row in the Commands table."
+3b. **Preflight (optional)** — "What command runs test, lint, and build together? If none, chain Test + Lint + Build into one **Preflight** row."
 4. **Architecture** — "Key modules and relationships in 1–2 sentences."
 5. **Conventions** — "Any naming, file organization, or patterns all agents must follow?"
 6. **Never-do list** — "What are the hard stops? Things an agent must never touch?"
 7. **Defensive code categories** — "Which apply? (Rate limit / Retry / Circuit breaker / Timeout / Graceful degradation)"
 8. **Local tool wiring (optional)** — "Wire bigpowers for project-local tools? (Cursor, OpenCode, Cline, Aider, Codex CLI)" If yes, generate AGENTS.md spine artifacts per [REFERENCE.md](REFERENCE.md) §Local tool wiring and §AGENTS.md spine. If no, skip — standard seed output unchanged (no AGENTS.md spine unless opted in).
 
+## Agentic STE for generated prose (e79s03)
+
+When writing instructional lines in `CLAUDE.md`, `AGENTS.md`, or `CONVENTIONS.md`, follow [AGENTIC-STE.md](../../docs/AGENTIC-STE.md):
+
+- Use directive vocabulary: MUST, MUST NOT, NEVER, ALWAYS, DO, DO NOT
+- Do NOT use hedge modals listed in AGENTIC-STE.md Rule 3
+- Cap each instruction sentence at 20 words
+- Write imperative, active-voice lines — one instruction per line
+- Do NOT apply Agentic STE to `terse-mode` (output compression is out of scope)
+
+After generation, run `bash scripts/validate-agentic-ste.sh --strict CLAUDE.md CONVENTIONS.md` when those files exist in the target project.
+
 ## Generate files
 
 After the interview, generate each file using the templates in [REFERENCE.md](REFERENCE.md):
@@ -64,9 +77,11 @@ echo "# Specs\n\nAll planning documents for this project." > specs/README.md
 
 **Note:** `specs/state.yaml.lock` is NOT pre-created — acquired/released dynamically.
 
-`specs/state.yaml` carries a top-level `workflow_mode` key (`team-pr` | `solo-git`, default `solo-git`). This is the **canonical integrate-mode signal** for all skills — set it once here and skills such as `release-branch` read it from this file instead of sniffing profile files.
+`specs/state.yaml` carries top-level `workflow_mode` (`team-pr` | `solo-git`, default `solo-git`).
+This is the **canonical integrate-mode signal** for all skills.
+Set it once here. Skills such as `release-branch` read this file instead of sniffing profiles.
 
-When generating `CLAUDE.md`, if the user did not name a Preflight command, chain the Test + Lint + Build interview answers into one **Preflight** row (e.g. `npm test && npm run lint && npm run build`).
+When generating `CLAUDE.md`, chain Test + Lint + Build into one **Preflight** row if the user named no Preflight command.
 
 ### Self-installing fenced markers (e45s21)
 
@@ -78,7 +93,9 @@ Skills that write into `CLAUDE.md` or `AGENTS.md` MUST use **fenced HTML comment
 <!-- END bigpowers:section-id -->
 ```
 
-**Merge rule:** On update, replace only the content *between* matching `BEGIN`/`END` pairs. If a marker pair is missing, append a new fenced block at the end of the file — never rewrite the whole file.
+**Merge rule:** On update, replace only content between matching `BEGIN`/`END` pairs.
+If a marker pair is missing, append a new fenced block at file end.
+Never rewrite the whole file.
 
 **Standard marker IDs** for seeded projects (see [REFERENCE.md](REFERENCE.md) § Fenced markers):
 

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

@@ -5,6 +5,7 @@ description: "Sequential subagent batch audit of the bigpowers skill catalog —
 
 # story: e09s01
 <!-- story: e45s12 -->
+<!-- story: e79s04 -->
 
 
 # Stocktake Skills
@@ -24,6 +25,7 @@ Audit SKILL.md catalog for drift, stale triggers, missing HARD GATEs, and INDEX
 ## Process
 
 0. **Catalog validator (code-enforced)** — run `bash scripts/validate-skill-catalog.sh`. Any FAIL is a critical finding before manual review. Add `--archive` to list zero-usage skills from `metrics.skill_timings` for auto-archiving candidates (move to `specs/epics/archive/` or delete after user confirms).
+0b. **Agentic STE audit (e79s04)** — run `bash scripts/validate-agentic-ste.sh --audit skills/`. Flag hedge words and sentences over 20 words per [AGENTIC-STE.md](../../docs/AGENTIC-STE.md). Record WARN lines in the stocktake report as **STE debt** — do NOT rewrite the full catalog in one pass. Route critical repeat offenders to `evolve-skill`.
 1. Run `bash scripts/audit-catalog.sh` to verify pi/skills ↔ source SKILL.md sync. Mismatch is a critical finding.
 2. Run mode; for each skill check: exists, verb-noun, &lt;300 lines total, HARD GATE present, INDEX row matches.
 3. Write `specs/STOCKTAKE-<date>.md` with findings table (skill, issue, severity).
@@ -55,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: `grep -c "Story" specs/release-plan.yaml 2>/dev/null || echo "no release plan"`
 
 ### 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`