bigpowers 2.44.1 → 2.45.1

package/.pi/package.json

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

package/.pi/prompts/align-grid.md

@@ -102,7 +102,3 @@ A clean run looks like: `col=0px overlay=0px baseline≤4px ink=0px` → `GRID V
 
 ## CREED
 A grid you can't toggle on and measure is a mood board, not a system. Build it from one source of truth, prove it at 0px, and align the **ink**.
-
-## Verify
-
-→ verify: `test -f align-grid/SKILL.md && grep -q '^name:' align-grid/SKILL.md && echo "OK: align-grid valid" || echo "FAIL: align-grid missing"`

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

@@ -121,7 +121,7 @@ Aggregate exit code: `0` if all sections PASS, `1` (non-zero) if any section FAI
 
 ## Verify
 
-→ verify: `test -f audit-code/SKILL.md && grep -q '^name:' audit-code/SKILL.md && echo "OK: audit-code valid" || echo "FAIL: audit-code missing"`
+→ verify: `test -f CONVENTIONS.md && test -d skills/enforce-first && test -d skills/request-review && echo "OK: audit-code dependencies present" || echo "FAIL"`
 
 
 ## Handoff

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

@@ -76,4 +76,4 @@ Write `handoff.next_skill` and `handoff.context` in `state.yaml` when pausing mi
 
 ## Verify
 
-→ verify: `test -f build-epic/SKILL.md && grep -q '^name:' build-epic/SKILL.md && echo "OK: build-epic valid" || echo "FAIL: build-epic missing"`
+→ 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"`

package/.pi/prompts/commit-message.md

@@ -46,9 +46,6 @@ If the repo uses a custom `@semantic-release/commit-analyzer` preset, note that
 
 - [REFERENCE.md](REFERENCE.md) — Message shape, footers, release mapping, squashing notes.
 
-## Verify
-
-→ verify: `test -f commit-message/SKILL.md && grep -q '^name:' commit-message/SKILL.md && echo "OK: commit-message valid" || echo "FAIL: commit-message missing"`
 
 
 ## Handoff

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

@@ -58,10 +58,6 @@ After drafting, verify:
 - [ ] specs/ output documented if applicable
 - [ ] `sync-skills.sh` run to propagate to Cursor/Gemini
 
-## Verify
-
-→ verify: `test -f craft-skill/SKILL.md && grep -q '^name:' craft-skill/SKILL.md && echo "OK: craft-skill valid" || echo "FAIL: craft-skill missing"`
-
 ---
 
 # Craft Skill — Reference

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

@@ -91,10 +91,6 @@ Side effects happen inline as decisions crystallize:
 - **User rejects the candidate with a load-bearing reason?** Offer an ADR, framed as: _"Want me to record this as an ADR so future architecture reviews don't re-suggest it?"_ Only offer when the reason would actually be needed by a future explorer. See [ADR-FORMAT.md](../model-domain/ADR-FORMAT.md).
 - **Want to explore alternative interfaces for the deepened module?** See [INTERFACE-DESIGN.md](INTERFACE-DESIGN.md).
 
-## Verify
-
-→ verify: `test -f deepen-architecture/SKILL.md && grep -q '^name:' deepen-architecture/SKILL.md && echo "OK: deepen-architecture valid" || echo "FAIL: deepen-architecture missing"`
-
 ---
 
 # Deepening

package/.pi/prompts/define-language.md

@@ -77,7 +77,3 @@ When invoked again in the same conversation:
 3. Update definitions if understanding has evolved
 4. Re-flag any new ambiguities
 5. Rewrite the example dialogue to incorporate new terms
-
-## Verify
-
-→ verify: `test -f define-language/SKILL.md && grep -q '^name:' define-language/SKILL.md && echo "OK: define-language valid" || echo "FAIL: define-language missing"`

package/.pi/prompts/define-success.md

@@ -62,5 +62,3 @@ Present the pairs to the user and ask: "Does this capture everything the task re
 Once confirmed, these pairs become the skeleton for `plan-work`'s steps. Pass them along when calling `plan-work`.
 
 ## Verify
-
-→ verify: `test -f define-success/SKILL.md && grep -q '^name:' define-success/SKILL.md && echo "OK: define-success valid" || echo "FAIL: define-success missing"`

package/.pi/prompts/delegate-task.md

@@ -74,7 +74,3 @@ Check:
 ```
 
 Report the decision and rationale to the user.
-
-## Verify
-
-→ verify: `test -f delegate-task/SKILL.md && grep -q '^name:' delegate-task/SKILL.md && echo "OK: delegate-task valid" || echo "FAIL: delegate-task missing"`

package/.pi/prompts/deploy.md

@@ -103,10 +103,6 @@ For comprehensive health-checking, chain to the `smoke-test` skill:
 bash scripts/run-smoke.sh "$DEPLOY_URL"
 ```
 
-## Verify
-
-→ verify: `test -f deploy/SKILL.md && grep -q '^name:' deploy/SKILL.md && echo "OK: deploy valid" || echo "FAIL: deploy missing"`
-
 ---
 
 # Deploy — Reference

package/.pi/prompts/design-interface.md

@@ -94,7 +94,3 @@ From "A Philosophy of Software Design":
 - Don't skip comparison — the value is in contrast
 - Don't implement — this is purely about interface shape
 - Don't evaluate based on implementation effort
-
-## Verify
-
-→ verify: `test -f design-interface/SKILL.md && grep -q '^name:' design-interface/SKILL.md && echo "OK: design-interface valid" || echo "FAIL: design-interface missing"`

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

@@ -93,9 +93,6 @@ If this cycle modified files in `.github/workflows/`, run the CI dry-run procedu
 [ ] verify: command passes
 ```
 
-## Verify
-
-→ verify: `test -f develop-tdd/SKILL.md && grep -q '^name:' develop-tdd/SKILL.md && echo "OK: develop-tdd valid" || echo "FAIL: develop-tdd missing"`
 
 
 ## Handoff

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

@@ -81,7 +81,3 @@ When all agents return:
 Merge accepted results. If any agent's result conflicts with another, resolve manually and note the conflict.
 
 Report a summary: which tasks succeeded, which need revision, and overall verify status.
-
-## Verify
-
-→ verify: `test -f dispatch-agents/SKILL.md && grep -q '^name:' dispatch-agents/SKILL.md && echo "OK: dispatch-agents valid" || echo "FAIL: dispatch-agents missing"`

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

@@ -20,7 +20,3 @@ Confirm the sections with the user.
 2. For each section:
 
 2a. Rewrite the section to improve clarity, coherence, and flow. Use maximum 240 characters per paragraph.
-
-## Verify
-
-→ verify: `test -f edit-document/SKILL.md && grep -q '^name:' edit-document/SKILL.md && echo "OK: edit-document valid" || echo "FAIL: edit-document missing"`

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

@@ -98,7 +98,3 @@ Once the spec is clear, recommend the next step:
 - If a spike is needed first → `spike-prototype`
 - If architecture decisions are needed → `deepen-architecture` or `grill-me`
 - If the plan depends on a specific library or API → `grill-me` in docs mode
-
-## Verify
-
-→ verify: `test -f elaborate-spec/SKILL.md && grep -q '^name:' elaborate-spec/SKILL.md && echo "OK: elaborate-spec valid" || echo "FAIL: elaborate-spec missing"`

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

@@ -80,7 +80,3 @@ For each failing criterion:
 4. Re-run the suite to confirm it still passes
 
 Report: "F.I.R.S.T audit complete. X criteria passed, Y fixed."
-
-## Verify
-
-→ verify: `test -f enforce-first/SKILL.md && grep -q '^name:' enforce-first/SKILL.md && echo "OK: enforce-first valid" || echo "FAIL: enforce-first missing"`

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

@@ -52,7 +52,3 @@ Suggest: `verify-work` → `run-evals` → `audit-code` → `simulate-agents`
 ## Rules
 
 - **Loop until behavioral correctness is verified**: if a verify command passes but the observed behavior is still wrong, return to step 1 and run the execution cycle again.
-
-## Verify
-
-→ verify: `test -f execute-plan/SKILL.md && grep -q '^name:' execute-plan/SKILL.md && echo "OK: execute-plan valid" || echo "FAIL: execute-plan missing"`

package/.pi/prompts/extract-design.md

@@ -75,10 +75,6 @@ node extract-design/tests/test-extraction.js
 
 See [REFERENCE.md](REFERENCE.md) for extraction algorithms and heuristics.
 
-## Verify
-
-→ verify: `test -f extract-design/SKILL.md && grep -q '^name:' extract-design/SKILL.md && echo "OK: extract-design valid" || echo "FAIL: extract-design missing"`
-
 ---
 
 # Extract Design — Reference

package/.pi/prompts/grill-me.md

@@ -28,10 +28,6 @@ Short form:
 4. Report confirmed ✓, corrected ✗ (with the real behavior), and uncertain → `spike-prototype`.
 5. Update the plan for each confirmed discrepancy.
 
-## Verify
-
-→ verify: `test -f grill-me/SKILL.md && grep -q '^name:' grill-me/SKILL.md && echo "OK: grill-me valid" || echo "FAIL: grill-me missing"`
-
 ---
 
 # Docs Mode — Full Process

package/.pi/prompts/guard-git.md

@@ -42,10 +42,6 @@ To add or remove patterns or protected branches, edit `pre-tool-use.sh`.
 
 Full JSON examples, merge rules, Antigravity deny-list entries, and test commands: [REFERENCE.md](REFERENCE.md).
 
-## Verify
-
-→ verify: `test -f guard-git/SKILL.md && grep -q '^name:' guard-git/SKILL.md && echo "OK: guard-git valid" || echo "FAIL: guard-git missing"`
-
 ---
 
 # Git guardrails — reference

package/.pi/prompts/hook-commits.md

@@ -91,7 +91,3 @@ This will run through the new pre-commit hooks — a good smoke test that everyt
 - Husky v9+ doesn't need shebangs in hook files
 - `prettier --ignore-unknown` skips files Prettier can't parse (images, etc.)
 - The pre-commit runs lint-staged first (fast, staged-only), then full typecheck and tests
-
-## Verify
-
-→ verify: `test -f hook-commits/SKILL.md && grep -q '^name:' hook-commits/SKILL.md && echo "OK: hook-commits valid" || echo "FAIL: hook-commits missing"`

package/.pi/prompts/inspect-quality.md

@@ -103,7 +103,3 @@ For each bug, also append a detail section:
 ### 5. Continue the session
 
 After logging, ask: "Next issue, or are we done?" Keep going until the user says done. Each issue is independent — don't batch them.
-
-## Verify
-
-→ verify: `test -f inspect-quality/SKILL.md && grep -q '^name:' inspect-quality/SKILL.md && echo "OK: inspect-quality valid" || echo "FAIL: inspect-quality missing"`

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

@@ -117,7 +117,3 @@ A numbered list of RED-GREEN cycles:
 </diagnosis-template>
 
 After writing the bug file, print a one-line summary of the root cause and suggest running `kickoff-branch` next to create a fix branch.
-
-## Verify
-
-→ verify: `test -f investigate-bug/SKILL.md && grep -q '^name:' investigate-bug/SKILL.md && echo "OK: investigate-bug valid" || echo "FAIL: investigate-bug missing"`

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

@@ -118,9 +118,6 @@ Ready to develop.
 
 Suggest next skill: `develop-tdd` to start the TDD loop, or `execute-plan` if `specs/release-plan.yaml + epic capsule directories` already exists.
 
-## Verify
-
-→ verify: `test -f kickoff-branch/SKILL.md && grep -q '^name:' kickoff-branch/SKILL.md && echo "OK: kickoff-branch valid" || echo "FAIL: kickoff-branch missing"`
 
 
 ## Handoff

package/.pi/prompts/map-codebase.md

@@ -68,7 +68,3 @@ Compile all findings into `specs/tech-architecture/tech-stack.md`. This file ser
 - Before a major refactor or architectural change.
 - When `survey-context` reveals a lack of domain knowledge.
 - To refresh `specs/tech-architecture/tech-stack.md` after significant changes.
-
-## Verify
-
-→ verify: `test -f map-codebase/SKILL.md && grep -q '^name:' map-codebase/SKILL.md && echo "OK: map-codebase valid" || echo "FAIL: map-codebase missing"`

package/.pi/prompts/model-domain.md

@@ -96,10 +96,6 @@ When the plan touches shared state, async, or multi-threaded code:
 - [ ] Flag **race risks** (check-then-act, non-atomic read-modify-write) with severity.
 - [ ] Record findings in `specs/tech-architecture/tech-stack.md` under `## Concurrency` or in an ADR if architectural.
 
-## Verify
-
-→ verify: `test -f model-domain/SKILL.md && grep -q '^name:' model-domain/SKILL.md && echo "OK: model-domain valid" || echo "FAIL: model-domain missing"`
-
 ---
 
 # ADR Format

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

@@ -45,7 +45,7 @@ See [REFERENCE.md](REFERENCE.md) for detailed phase specifications and gate type
 
 1. **Maintains state.yaml** — Tracks current phase, `active_epic`, `active_flow`, decisions, risks.
 2. **Spawns appropriate skills** — Routes by `model:` frontmatter. Decisions pass only via `specs/state.yaml` `handoff` between spawns.
-3. **Methodology lenses** — If `specs/tech-architecture/test.md` or ADRs exist, apply at phase gates.
+3. **Methodology lenses** — If `specs/tech-architecture/TEST_PLAN_LATEST.md` or ADRs exist, apply at phase gates.
 4. **Enforces gates** — Hard stops if success criteria not met.
 5. **The Gatekeeper** — Between stories in BUILD: read `specs/execution-status.yaml`; previous story must be `done` before starting the next; use `build-epic` for the 8-step epic cycle.
 6. **Pauses for confirmation** — After each phase, asks "Ready to proceed?".
@@ -66,10 +66,6 @@ All phases complete with artifacts:
 verify: test -f specs/state.yaml && test -f specs/release-plan.yaml && test -f specs/product/SCOPE_LATEST.yaml && ls specs/epics/*.yaml 1>/dev/null && echo "✅ All phases complete"
 ```
 
-## Verify
-
-→ verify: `test -f orchestrate-project/SKILL.md && grep -q '^name:' orchestrate-project/SKILL.md && echo "OK: orchestrate-project valid" || echo "FAIL: orchestrate-project missing"`
-
 ---
 
 # Orchestrate Reference: Phases, Modes, and Workflows

package/.pi/prompts/organize-workspace.md

@@ -75,10 +75,6 @@ Do this when the repo is under Git and the cleanup surfaced **untracked** noise:
 
 See [REFERENCE.md](REFERENCE.md) for shell patterns, `.gitignore` mechanics, and safety checks.
 
-## Verify
-
-→ verify: `test -f organize-workspace/SKILL.md && grep -q '^name:' organize-workspace/SKILL.md && echo "OK: organize-workspace valid" || echo "FAIL: organize-workspace missing"`
-
 ---
 
 # clean-my-room — reference patterns

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

@@ -77,5 +77,3 @@ Any further notes about the refactor.
 After writing `specs/REFACTOR_LATEST.md`, suggest running `kickoff-branch` next to create a refactor branch.
 
 ## Verify
-
-→ verify: `test -f plan-refactor/SKILL.md && grep -q '^name:' plan-refactor/SKILL.md && echo "OK: plan-refactor valid" || echo "FAIL: plan-refactor missing"`

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

@@ -52,7 +52,6 @@ After writing capsule tasks, suggest `kickoff-branch` (if not already on a featu
 
 ## Verify
 
-→ verify: `test -f plan-work/SKILL.md && grep -q '^name:' plan-work/SKILL.md && echo "OK: plan-work valid" || echo "FAIL: plan-work missing"`
 
 
 ## Handoff

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

@@ -94,9 +94,6 @@ Skipped skills (justified for data-only change):
 
 Invoke `release-branch` to merge and ship.
 
-## Verify
-
-→ verify: `test -f quick-fix/SKILL.md && grep -q '^name:' quick-fix/SKILL.md && echo "OK: quick-fix valid" || echo "FAIL: quick-fix missing"`
 
 ## Example
 

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

@@ -129,7 +129,7 @@ Report: "Branch released. Integrate mode: <solo-local|team-pr>. cwd: $(pwd) on $
 
 ## Verify
 
-→ verify: `test -f release-branch/SKILL.md && grep -q '^name:' release-branch/SKILL.md && echo "OK: release-branch valid" || echo "FAIL: release-branch missing"`
+→ 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"`
 
 ---
 

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

@@ -69,7 +69,3 @@ When the reviewer returns:
 Pass the reviewer's report to `respond-review` to categorize findings and apply fixes.
 
 Report to user: "Review complete. [N] findings: [X] must-fix, [Y] should-fix, [Z] consider. Running respond-review."
-
-## Verify
-
-→ verify: `test -f request-review/SKILL.md && grep -q '^name:' request-review/SKILL.md && echo "OK: request-review valid" || echo "FAIL: request-review missing"`

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

@@ -68,7 +68,3 @@ All tests pass.
 ```
 
 Suggest next skill: `commit-message`.
-
-## Verify
-
-→ verify: `test -f respond-review/SKILL.md && grep -q '^name:' respond-review/SKILL.md && echo "OK: respond-review valid" || echo "FAIL: respond-review missing"`

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

@@ -52,7 +52,6 @@ Each finding: **`File:Line` — Severity — Category**
 
 ## Verify
 
-→ verify: `test -f security-review/SKILL.md && grep -q '^name:' security-review/SKILL.md && echo "OK: security-review valid" || echo "FAIL: security-review missing"`
 
 
 ```bash

package/.pi/prompts/seed-conventions.md

@@ -43,8 +43,8 @@ mkdir -p specs/product specs/product/snapshots specs/epics/archive
 mkdir -p specs/tech-architecture specs/adr specs/verifications specs/bugs
 touch specs/product/SCOPE_LATEST.yaml specs/product/VISION_LATEST.yaml specs/product/GLOSSARY_LATEST.yaml
 touch specs/release-plan.yaml specs/execution-status.yaml specs/planning-status.yaml specs/state.yaml
-touch specs/tech-architecture/tech-stack.md specs/tech-architecture/security.md
-touch specs/tech-architecture/test.md specs/tech-architecture/design.md
+touch specs/tech-architecture/tech-stack.md specs/tech-architecture/SECURITY_PLAN_LATEST.md
+touch specs/tech-architecture/TEST_PLAN_LATEST.md specs/tech-architecture/DESIGN_PLAN_LATEST.md
 touch specs/tech-architecture/REFACTOR_LATEST.md specs/tech-architecture/IMPACT_LATEST.md
 touch specs/bugs/registry.yaml
 echo "# Specs\n\nAll planning documents for this project." > specs/README.md
@@ -54,9 +54,6 @@ echo "# Specs\n\nAll planning documents for this project." > specs/README.md
 
 `specs/state.yaml` carries a top-level `workflow_mode` key (`team-pr` | `solo-git`, default `team-pr`). 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.
 
-## Verify
-
-→ verify: `test -f seed-conventions/SKILL.md && grep -q '^name:' seed-conventions/SKILL.md && echo "OK: seed-conventions valid" || echo "FAIL: seed-conventions missing"`
 
 
 - [ ] CLAUDE.md exists and is populated

package/.pi/prompts/smoke-test.md

@@ -64,10 +64,6 @@ The `deploy` skill references `smoke-test` as its final verification step:
 DEPLOY_URL="$DEPLOY_URL" bash scripts/run-smoke.sh
 ```
 
-## Verify
-
-→ verify: `test -f smoke-test/SKILL.md && grep -q '^name:' smoke-test/SKILL.md && echo "OK: smoke-test valid" || echo "FAIL: smoke-test missing"`
-
 ---
 
 # Smoke Test — Reference

package/.pi/prompts/spike-prototype.md

@@ -92,7 +92,3 @@ After writing the findings, delete or discard the spike code. It is not meant to
 ### 6. Feed back into plan-work
 
 The spike findings are the input to `plan-work`. Call `plan-work` next, informed by `specs/archive/spikes/SPIKE-<name>.md`.
-
-## Verify
-
-→ verify: `test -f spike-prototype/SKILL.md && grep -q '^name:' spike-prototype/SKILL.md && echo "OK: spike-prototype valid" || echo "FAIL: spike-prototype missing"`

package/.pi/prompts/terse-mode.md

@@ -35,7 +35,3 @@ Example — destructive op:
 > ```
 >
 > Terse resume. Verify backup exist first.
-
-## Verify
-
-→ verify: `test -f terse-mode/SKILL.md && grep -q '^name:' terse-mode/SKILL.md && echo "OK: terse-mode valid" || echo "FAIL: terse-mode missing"`

package/.pi/prompts/using-bigpowers.md

@@ -103,7 +103,3 @@ Start the HTTP dashboard with `visual-dashboard` → `GET /api/status?projectDir
 ## After this
 
 Call `survey-context` to read your project's current state and get a personalized recommendation for where to go next.
-
-## Verify
-
-→ verify: `test -f using-bigpowers/SKILL.md && grep -q '^name:' using-bigpowers/SKILL.md && echo "OK: using-bigpowers valid" || echo "FAIL: using-bigpowers missing"`

package/.pi/prompts/validate-contracts.md

@@ -109,10 +109,6 @@ bash scripts/validate-contracts.sh <contract-file>
 # → All pass → ready to deploy
 ```
 
-## Verify
-
-→ verify: `test -f validate-contracts/SKILL.md && grep -q '^name:' validate-contracts/SKILL.md && echo "OK: validate-contracts valid" || echo "FAIL: validate-contracts missing"`
-
 ---
 
 # Validate Contracts — Reference

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

@@ -101,7 +101,3 @@ Mechanical verification (tests passing) is only half the fix. You must prove **b
 - **The verify command from specs/bugs/BUG-*.md or the active epic task `verify` field must pass**
 
 Suggest next skill: `audit-code` → `commit-message`.
-
-## Verify
-
-→ verify: `test -f validate-fix/SKILL.md && grep -q '^name:' validate-fix/SKILL.md && echo "OK: validate-fix valid" || echo "FAIL: validate-fix missing"`

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

@@ -90,7 +90,3 @@ Place setup scripts in `scripts/setup.sh` (or language-appropriate equivalent).
 - [ ] Run `scripts/setup.sh` twice — second run should produce no errors
 - [ ] Health check command returns success
 - [ ] No sensitive data in log output
-
-## Verify
-
-→ verify: `test -f wire-observability/SKILL.md && grep -q '^name:' wire-observability/SKILL.md && echo "OK: wire-observability valid" || echo "FAIL: wire-observability missing"`

package/.pi/skills/align-grid/SKILL.md

@@ -104,7 +104,3 @@ A clean run looks like: `col=0px overlay=0px baseline≤4px ink=0px` → `GRID V
 
 ## CREED
 A grid you can't toggle on and measure is a mood board, not a system. Build it from one source of truth, prove it at 0px, and align the **ink**.
-
-## Verify
-
-→ verify: `test -f align-grid/SKILL.md && grep -q '^name:' align-grid/SKILL.md && echo "OK: align-grid valid" || echo "FAIL: align-grid missing"`

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

@@ -123,7 +123,7 @@ Aggregate exit code: `0` if all sections PASS, `1` (non-zero) if any section FAI
 
 ## Verify
 
-→ verify: `test -f audit-code/SKILL.md && grep -q '^name:' audit-code/SKILL.md && echo "OK: audit-code valid" || echo "FAIL: audit-code missing"`
+→ verify: `test -f CONVENTIONS.md && test -d skills/enforce-first && test -d skills/request-review && echo "OK: audit-code dependencies present" || echo "FAIL"`
 
 
 ## Handoff

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

@@ -78,4 +78,4 @@ Write `handoff.next_skill` and `handoff.context` in `state.yaml` when pausing mi
 
 ## Verify
 
-→ verify: `test -f build-epic/SKILL.md && grep -q '^name:' build-epic/SKILL.md && echo "OK: build-epic valid" || echo "FAIL: build-epic missing"`
+→ 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"`

package/.pi/skills/commit-message/SKILL.md

@@ -48,9 +48,6 @@ If the repo uses a custom `@semantic-release/commit-analyzer` preset, note that
 
 - [REFERENCE.md](REFERENCE.md) — Message shape, footers, release mapping, squashing notes.
 
-## Verify
-
-→ verify: `test -f commit-message/SKILL.md && grep -q '^name:' commit-message/SKILL.md && echo "OK: commit-message valid" || echo "FAIL: commit-message missing"`
 
 
 ## Handoff

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

@@ -60,10 +60,6 @@ After drafting, verify:
 - [ ] specs/ output documented if applicable
 - [ ] `sync-skills.sh` run to propagate to Cursor/Gemini
 
-## Verify
-
-→ verify: `test -f craft-skill/SKILL.md && grep -q '^name:' craft-skill/SKILL.md && echo "OK: craft-skill valid" || echo "FAIL: craft-skill missing"`
-
 ---
 
 # Craft Skill — Reference

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

@@ -93,10 +93,6 @@ Side effects happen inline as decisions crystallize:
 - **User rejects the candidate with a load-bearing reason?** Offer an ADR, framed as: _"Want me to record this as an ADR so future architecture reviews don't re-suggest it?"_ Only offer when the reason would actually be needed by a future explorer. See [ADR-FORMAT.md](../model-domain/ADR-FORMAT.md).
 - **Want to explore alternative interfaces for the deepened module?** See [INTERFACE-DESIGN.md](INTERFACE-DESIGN.md).
 
-## Verify
-
-→ verify: `test -f deepen-architecture/SKILL.md && grep -q '^name:' deepen-architecture/SKILL.md && echo "OK: deepen-architecture valid" || echo "FAIL: deepen-architecture missing"`
-
 ---
 
 # Deepening

package/.pi/skills/define-language/SKILL.md

@@ -79,7 +79,3 @@ When invoked again in the same conversation:
 3. Update definitions if understanding has evolved
 4. Re-flag any new ambiguities
 5. Rewrite the example dialogue to incorporate new terms
-
-## Verify
-
-→ verify: `test -f define-language/SKILL.md && grep -q '^name:' define-language/SKILL.md && echo "OK: define-language valid" || echo "FAIL: define-language missing"`

package/.pi/skills/define-success/SKILL.md

@@ -64,5 +64,3 @@ Present the pairs to the user and ask: "Does this capture everything the task re
 Once confirmed, these pairs become the skeleton for `plan-work`'s steps. Pass them along when calling `plan-work`.
 
 ## Verify
-
-→ verify: `test -f define-success/SKILL.md && grep -q '^name:' define-success/SKILL.md && echo "OK: define-success valid" || echo "FAIL: define-success missing"`

package/.pi/skills/delegate-task/SKILL.md

@@ -76,7 +76,3 @@ Check:
 ```
 
 Report the decision and rationale to the user.
-
-## Verify
-
-→ verify: `test -f delegate-task/SKILL.md && grep -q '^name:' delegate-task/SKILL.md && echo "OK: delegate-task valid" || echo "FAIL: delegate-task missing"`

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

@@ -105,10 +105,6 @@ For comprehensive health-checking, chain to the `smoke-test` skill:
 bash scripts/run-smoke.sh "$DEPLOY_URL"
 ```
 
-## Verify
-
-→ verify: `test -f deploy/SKILL.md && grep -q '^name:' deploy/SKILL.md && echo "OK: deploy valid" || echo "FAIL: deploy missing"`
-
 ---
 
 # Deploy — Reference

package/.pi/skills/design-interface/SKILL.md

@@ -96,7 +96,3 @@ From "A Philosophy of Software Design":
 - Don't skip comparison — the value is in contrast
 - Don't implement — this is purely about interface shape
 - Don't evaluate based on implementation effort
-
-## Verify
-
-→ verify: `test -f design-interface/SKILL.md && grep -q '^name:' design-interface/SKILL.md && echo "OK: design-interface valid" || echo "FAIL: design-interface missing"`

package/.pi/skills/develop-tdd/SKILL.md

@@ -95,9 +95,6 @@ If this cycle modified files in `.github/workflows/`, run the CI dry-run procedu
 [ ] verify: command passes
 ```
 
-## Verify
-
-→ verify: `test -f develop-tdd/SKILL.md && grep -q '^name:' develop-tdd/SKILL.md && echo "OK: develop-tdd valid" || echo "FAIL: develop-tdd missing"`
 
 
 ## Handoff

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

@@ -83,7 +83,3 @@ When all agents return:
 Merge accepted results. If any agent's result conflicts with another, resolve manually and note the conflict.
 
 Report a summary: which tasks succeeded, which need revision, and overall verify status.
-
-## Verify
-
-→ verify: `test -f dispatch-agents/SKILL.md && grep -q '^name:' dispatch-agents/SKILL.md && echo "OK: dispatch-agents valid" || echo "FAIL: dispatch-agents missing"`

package/.pi/skills/edit-document/SKILL.md

@@ -22,7 +22,3 @@ Confirm the sections with the user.
 2. For each section:
 
 2a. Rewrite the section to improve clarity, coherence, and flow. Use maximum 240 characters per paragraph.
-
-## Verify
-
-→ verify: `test -f edit-document/SKILL.md && grep -q '^name:' edit-document/SKILL.md && echo "OK: edit-document valid" || echo "FAIL: edit-document missing"`

package/.pi/skills/elaborate-spec/SKILL.md

@@ -100,7 +100,3 @@ Once the spec is clear, recommend the next step:
 - If a spike is needed first → `spike-prototype`
 - If architecture decisions are needed → `deepen-architecture` or `grill-me`
 - If the plan depends on a specific library or API → `grill-me` in docs mode
-
-## Verify
-
-→ verify: `test -f elaborate-spec/SKILL.md && grep -q '^name:' elaborate-spec/SKILL.md && echo "OK: elaborate-spec valid" || echo "FAIL: elaborate-spec missing"`