bigpowers 2.45.0 → 2.45.2

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

@@ -77,10 +77,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/skills/grill-me/SKILL.md

@@ -30,10 +30,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/skills/guard-git/SKILL.md

@@ -44,10 +44,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/skills/hook-commits/SKILL.md

@@ -93,7 +93,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/skills/inspect-quality/SKILL.md

@@ -105,7 +105,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/skills/investigate-bug/SKILL.md

@@ -119,7 +119,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/skills/kickoff-branch/SKILL.md

@@ -120,9 +120,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/skills/map-codebase/SKILL.md

@@ -70,7 +70,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/skills/model-domain/SKILL.md

@@ -98,10 +98,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/skills/orchestrate-project/SKILL.md

@@ -68,10 +68,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/skills/organize-workspace/SKILL.md

@@ -77,10 +77,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/skills/plan-refactor/SKILL.md

@@ -79,5 +79,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/skills/plan-work/SKILL.md

@@ -54,7 +54,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/skills/quick-fix/SKILL.md

@@ -96,9 +96,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/skills/release-branch/SKILL.md

@@ -131,7 +131,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/skills/request-review/SKILL.md

@@ -71,7 +71,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/skills/respond-review/SKILL.md

@@ -70,7 +70,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/skills/security-review/SKILL.md

@@ -54,7 +54,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/skills/seed-conventions/SKILL.md

@@ -56,9 +56,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/skills/smoke-test/SKILL.md

@@ -66,10 +66,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/skills/spike-prototype/SKILL.md

@@ -94,7 +94,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/skills/terse-mode/SKILL.md

@@ -37,7 +37,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/skills/using-bigpowers/SKILL.md

@@ -105,7 +105,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/skills/validate-contracts/SKILL.md

@@ -111,10 +111,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/skills/validate-fix/SKILL.md

@@ -103,7 +103,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/skills/wire-observability/SKILL.md

@@ -92,7 +92,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/CHANGELOG.md

@@ -1,3 +1,17 @@
+## [2.45.2](https://github.com/danielvm-git/bigpowers/compare/v2.45.1...v2.45.2) (2026-07-03)
+
+
+### Bug Fixes
+
+* **sync:** sync stale .pi/package.json version to 2.45.1 ([4901405](https://github.com/danielvm-git/bigpowers/commit/49014051a42a63c9499d8aedc379ae7348fbb235))
+
+## [2.45.1](https://github.com/danielvm-git/bigpowers/compare/v2.45.0...v2.45.1) (2026-07-02)
+
+
+### Bug Fixes
+
+* **skills:** remove 43 tautological verify commands, add behavior checks to critical-path skills ([8823212](https://github.com/danielvm-git/bigpowers/commit/88232125b8ee25b74dfa765a2d839d3d95e80d9e)), closes [#37](https://github.com/danielvm-git/bigpowers/issues/37) [#39](https://github.com/danielvm-git/bigpowers/issues/39) [#40](https://github.com/danielvm-git/bigpowers/issues/40) [#41](https://github.com/danielvm-git/bigpowers/issues/41) [#42](https://github.com/danielvm-git/bigpowers/issues/42)
+
 # [2.45.0](https://github.com/danielvm-git/bigpowers/compare/v2.44.1...v2.45.0) (2026-07-02)
 
 

package/CLAUDE.md

@@ -17,6 +17,8 @@ Stack: Markdown / Bash (documentation-based; skills integrate with Claude Code,
 | Build   | `bash scripts/install.sh` (from source) |
 | Lint    | `bash scripts/sync-skills.sh` (validates SKILL.md syntax) |
 | Validate specs YAML | `bash scripts/validate-specs-yaml.sh` |
+| Typecheck | N/A (Markdown / Bash project) |
+| CI platform | GitHub Actions (`.github/workflows/publish.yml`, `sync-skills.yml`) |
 | Compliance | `npm run compliance` |
 
 ## Architecture

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.45.0",
+  "version": "2.45.2",
   "description": "72 agent skills synthesizing 17 years of software engineering discipline into a prescriptive methodology for solo developers",
   "main": "index.js",
   "scripts": {

package/skills/align-grid/SKILL.md

@@ -109,6 +109,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/skills/audit-code/SKILL.md

@@ -122,7 +122,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/skills/build-epic/SKILL.md

@@ -77,4 +77,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/skills/commit-message/SKILL.md

@@ -47,9 +47,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/skills/craft-skill/SKILL.md

@@ -59,6 +59,3 @@ 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"`

package/skills/deepen-architecture/SKILL.md

@@ -92,6 +92,3 @@ 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"`

package/skills/define-language/SKILL.md

@@ -79,6 +79,3 @@ When invoked again in the same conversation:
 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/skills/define-success/SKILL.md

@@ -66,4 +66,3 @@ Once confirmed, these pairs become the skeleton for `plan-work`'s steps. Pass th
 
 ## 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/skills/delegate-task/SKILL.md

@@ -76,6 +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/skills/deploy/SKILL.md

@@ -104,6 +104,3 @@ 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"`

package/skills/design-interface/SKILL.md

@@ -96,6 +96,3 @@ From "A Philosophy of Software Design":
 - 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/skills/develop-tdd/SKILL.md

@@ -94,9 +94,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/skills/dispatch-agents/SKILL.md

@@ -83,6 +83,3 @@ Merge accepted results. If any agent's result conflicts with another, resolve ma
 
 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/skills/edit-document/SKILL.md

@@ -22,6 +22,3 @@ Confirm the sections with the user.
 
 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/skills/elaborate-spec/SKILL.md

@@ -100,6 +100,3 @@ Once the spec is clear, recommend the next step:
 - 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/skills/enforce-first/SKILL.md

@@ -82,6 +82,3 @@ For each failing criterion:
 
 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/skills/execute-plan/SKILL.md

@@ -54,6 +54,3 @@ Suggest: `verify-work` → `run-evals` → `audit-code` → `simulate-agents`
 
 - **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/skills/extract-design/SKILL.md

@@ -76,6 +76,3 @@ 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"`

package/skills/grill-me/SKILL.md

@@ -29,6 +29,3 @@ 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"`

package/skills/guard-git/SKILL.md

@@ -43,6 +43,3 @@ 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"`

package/skills/hook-commits/SKILL.md

@@ -93,6 +93,3 @@ This will run through the new pre-commit hooks — a good smoke test that everyt
 - `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/skills/inspect-quality/SKILL.md

@@ -105,6 +105,3 @@ For each bug, also append a detail section:
 
 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/skills/investigate-bug/SKILL.md

@@ -119,6 +119,3 @@ A numbered list of RED-GREEN cycles:
 
 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/skills/kickoff-branch/SKILL.md

@@ -119,9 +119,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/skills/map-codebase/SKILL.md

@@ -70,6 +70,3 @@ Compile all findings into `specs/tech-architecture/tech-stack.md`. This file ser
 - 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/skills/model-domain/SKILL.md

@@ -97,6 +97,3 @@ 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"`

package/skills/orchestrate-project/SKILL.md

@@ -67,6 +67,3 @@ 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"`

package/skills/organize-workspace/SKILL.md

@@ -76,6 +76,3 @@ 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"`

package/skills/plan-refactor/SKILL.md

@@ -79,4 +79,3 @@ After writing `specs/REFACTOR_LATEST.md`, suggest running `kickoff-branch` next
 
 ## 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/skills/plan-work/SKILL.md

@@ -53,7 +53,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/skills/quick-fix/SKILL.md

@@ -95,9 +95,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/skills/release-branch/SKILL.md

@@ -130,4 +130,4 @@ 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/skills/request-review/SKILL.md

@@ -71,6 +71,3 @@ Pass the reviewer's report to `respond-review` to categorize findings and apply
 
 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/skills/respond-review/SKILL.md

@@ -70,6 +70,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/skills/security-review/SKILL.md

@@ -58,7 +58,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