bigpowers 2.43.2 → 2.43.4

package/hook-commits/SKILL.md

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

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

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

@@ -119,6 +119,11 @@ 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
 
 Gate: READY -> next: develop-tdd

package/map-codebase/SKILL.md

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

@@ -96,3 +96,7 @@ When the plan touches shared state, async, or multi-threaded code:
 - [ ] For each: who reads, who writes, synchronization mechanism (lock, actor, immutable copy).
 - [ ] 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/orchestrate-project/SKILL.md

@@ -66,3 +66,7 @@ All phases complete with artifacts:
 ```bash
 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/organize-workspace/SKILL.md

@@ -75,3 +75,7 @@ Do this when the repo is under Git and the cleanup surfaced **untracked** noise:
 5. **Verify**: run `git check-ignore -v <path>` on 2–3 representative paths.
 
 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/package.json

@@ -1,7 +1,7 @@
 {
   "name": "bigpowers",
-  "version": "2.43.2",
-  "description": "70 agent skills for spec-driven, test-first software development by solo developers",
+  "version": "2.43.4",
+  "description": "72 agent skills synthesizing 17 years of software engineering discipline into a prescriptive methodology for solo developers",
   "main": "index.js",
   "scripts": {
     "compliance": "bash scripts/audit-compliance.sh specs/verifications/features && bash scripts/validate-doctrine.sh",

package/plan-refactor/SKILL.md

@@ -76,3 +76,7 @@ Any further notes about the refactor.
 </refactor-plan-template>
 
 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/plan-work/SKILL.md

@@ -51,6 +51,11 @@ If this plan touches an existing module, run `assess-impact` first to understand
 
 After writing capsule tasks, suggest `kickoff-branch` (if not already on a feature branch) then `build-epic`, `execute-plan`, or `develop-tdd`.
 
+## 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
 
 Gate: READY -> next: kickoff-branch

package/quick-fix/SKILL.md

@@ -97,6 +97,9 @@ 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"`
+
+
 ```bash
 test -f quick-fix/SKILL.md && echo "OK: skill file exists" || echo "FAIL: no skill file"
 grep -q "name: quick-fix" quick-fix/SKILL.md && echo "OK: frontmatter" || echo "FAIL: frontmatter"

package/release-branch/SKILL.md

@@ -127,3 +127,7 @@ git checkout main && git status && pwd
 ```
 
 Report: "Branch released. Integrate mode: <solo-local|team-pr>. cwd: $(pwd) on $(git branch --show-current)."
+
+## 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"`

package/request-review/SKILL.md

@@ -70,3 +70,7 @@ 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/reset-baseline/SKILL.md

@@ -18,4 +18,4 @@ model: haiku
 
 ## Verify
 
-→ verify: `git status --short | wc -l | awk '{if($1==0) print "OK"; else print "DIRTY:" $1}'
+→ verify: `git status --short | wc -l | awk '{if($1==0) print "OK"; else print "DIRTY:" $1}'`

package/respond-review/SKILL.md

@@ -69,3 +69,7 @@ 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/scripts/run-skill-verify.sh

@@ -7,6 +7,15 @@
 
 set -uo pipefail
 
+# Portable timeout: macOS lacks GNU timeout; use perl alarm as fallback.
+if command -v timeout >/dev/null 2>&1; then
+  run_with_timeout() { timeout 10 bash -c "$1" 2>&1; }
+elif command -v perl >/dev/null 2>&1; then
+  run_with_timeout() { perl -e 'alarm 10; exec @ARGV' bash -c "$1" 2>&1; }
+else
+  run_with_timeout() { bash -c "$1" 2>&1; }
+fi
+
 REPO_ROOT="$(cd "$(dirname "$0")/.." && pwd)"
 cd "$REPO_ROOT"
 
@@ -18,8 +27,10 @@ run_skill() {
   local skill
   skill=$(dirname "$skill_md")
 
+  # Only match → verify: at line start (after optional blockquote "> " or numbered-list prefix)
+  # This prevents false matches against description prose or template examples.
   local cmd
-  cmd=$(grep '→ verify:' "$skill_md" 2>/dev/null | head -1 | sed 's/.*→ verify: *//')
+  cmd=$(grep -E '^(> )?→ verify:' "$skill_md" 2>/dev/null | head -1 | sed 's/^> // ; s/^→ verify: *//')
 
   if [ -z "$cmd" ]; then
     echo "SKIP: $skill"
@@ -27,8 +38,21 @@ run_skill() {
     return
   fi
 
+  # Strip surrounding backticks — SKILL.md verify: commands use markdown code-span wrapping
+  # but bash -c would interpret the backticks as command substitution, causing false FAILs.
+  cmd=$(echo "$cmd" | sed 's/^`//; s/`$//')
+
+  # Skip verify directives that are prose, not executable shell commands.
+  # Heuristic: if the command doesn't start with a known command word or path,
+  # it's likely descriptive text, not a runnable verification.
+  if ! echo "$cmd" | grep -qE '^[a-zA-Z][a-zA-Z0-9_.-]*\b|^\['; then
+    echo "SKIP: $skill (non-executable verify)"
+    SKIP=$((SKIP + 1))
+    return
+  fi
+
   local output
-  if output=$(timeout 10 bash -c "$cmd" 2>&1); then
+  if output=$(run_with_timeout "$cmd"); then
     echo "PASS: $skill"
     PASS=$((PASS + 1))
   else

package/security-review/SKILL.md

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

package/seed-conventions/SKILL.md

@@ -57,6 +57,9 @@ echo "# Specs\n\nAll planning documents for this project." > specs/README.md
 
 ## 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
 - [ ] CONVENTIONS.md exists and includes specs/ output convention
 - [ ] specs/product/ exists with SCOPE_LATEST.yaml, VISION_LATEST.yaml, GLOSSARY_LATEST.yaml

package/setup-environment/SKILL.md

@@ -21,4 +21,4 @@ Idempotent prep so BUILD phase commands succeed on first run.
 
 ## Verify
 
-→ verify: commands from CLAUDE.md Test/Lint rows exit 0
+→ verify: `test -f CLAUDE.md && grep -q 'Test' CLAUDE.md && echo "OK: CLAUDE.md has test table" || echo "MISSING: test commands"`

package/simulate-agents/SKILL.md

@@ -23,4 +23,4 @@ Two roles, **isolated contexts** (no shared state with BUILD agent):
 
 ## Verify
 
-→ verify: `test -f specs/SIMULATION-*.md && grep -c "Mock User\|Auditor" specs/SIMULATION-*.md | awk '{if($1>=2) print "OK"}'`
+→ 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"`

package/skills-lock.json

@@ -3,7 +3,7 @@
   "skills": {
     "align-grid": {
       "description": "\"Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid \\\"bands\\\" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's ink (not its box) on the line. Ships with a scaffold generator and a Puppeteer verification harness that proves 0px adherence.\"",
-      "sha256": "fe975bdd77773c2c",
+      "sha256": "6d76f83d71c5bd27",
       "path": "align-grid/SKILL.md"
     },
     "assess-impact": {
@@ -13,7 +13,7 @@
     },
     "audit-code": {
       "description": "Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.",
-      "sha256": "2e67f9125e0bec7c",
+      "sha256": "0d07d2fca30c1f2d",
       "path": "audit-code/SKILL.md"
     },
     "audit-plan": {
@@ -23,7 +23,7 @@
     },
     "build-epic": {
       "description": "Eight-step epic build cycle — reads state.yaml, execution-status.yaml, and one epic capsule; updates status via bp-yaml-set or direct edit. Resume mode runs one step per invocation. Use instead of ad-hoc execute-plan for release work.",
-      "sha256": "565d8396889dd9c9",
+      "sha256": "27128c418f7e546c",
       "path": "build-epic/SKILL.md"
     },
     "change-request": {
@@ -33,7 +33,7 @@
     },
     "commit-message": {
       "description": "Reviews working-tree changes, then drafts a Conventional Commits title/body and states the semantic-release version bump a single such commit would imply. Also notes which defensive-code categories were touched. Use when the user wants to commit recent work, prepare a Conventional Commits message, or asks for semantic-release / semver-consistent messaging before git commit.",
-      "sha256": "aeb104cdbd19b73e",
+      "sha256": "4272ff777f9f43de",
       "path": "commit-message/SKILL.md"
     },
     "compose-workflow": {
@@ -43,42 +43,42 @@
     },
     "craft-skill": {
       "description": "Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.",
-      "sha256": "9ca6eb728e98bf54",
+      "sha256": "8660de5647b77bd8",
       "path": "craft-skill/SKILL.md"
     },
     "deepen-architecture": {
       "description": "Find deepening opportunities in a codebase, informed by the domain language in specs/tech-architecture/tech-stack.md and the decisions in specs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.",
-      "sha256": "8424813a8c638a5b",
+      "sha256": "6f483d1c366613f3",
       "path": "deepen-architecture/SKILL.md"
     },
     "define-language": {
       "description": "Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to specs/UBIQUITOUS_LANGUAGE_LATEST.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".",
-      "sha256": "bffe0227335e5a41",
+      "sha256": "6cead64f3b818922",
       "path": "define-language/SKILL.md"
     },
     "define-success": {
       "description": "Convert an imperative task statement into explicit \"step → verify: <cmd>\" pairs before implementation begins. Use before plan-work when success criteria are unclear, when a task lacks verifiable checkpoints, or when user says \"how will we know this is done?\".",
-      "sha256": "8e03d23896f179fb",
+      "sha256": "21353242357ce913",
       "path": "define-success/SKILL.md"
     },
     "delegate-task": {
       "description": "Delegate one complex task to a single subagent, review its work in two stages before merging back. Sequential — one agent at a time, with oversight. Use when a task is complex and requires careful review before the result is accepted. Distinct from dispatch-agents (no parallelism here; reviewer sees full diff before proceeding).",
-      "sha256": "9e3b8bd7274def42",
+      "sha256": "95c1ccce9af5dfd0",
       "path": "delegate-task/SKILL.md"
     },
     "deploy": {
       "description": "\"Build → verify artifact → deploy → wait → smoke deployment pipeline. Platform-agnostic (MCP or CLI), with configurable timeout, retry with exponential backoff, and integrated health-check. The deploy half of CI/CD: run after build to push to production.\"",
-      "sha256": "304967c4f7d0ea13",
+      "sha256": "9c62a42e064f5c04",
       "path": "deploy/SKILL.md"
     },
     "design-interface": {
       "description": "Generate multiple radically different interface designs for a module using parallel sub-agents, then compare trade-offs. Based on \"Design It Twice\" from A Philosophy of Software Design. Use when user wants to design an API, explore interface options, compare module shapes, or mentions \"design it twice\".",
-      "sha256": "c93e3fe065857cb8",
+      "sha256": "f9f88fc01371f648",
       "path": "design-interface/SKILL.md"
     },
     "develop-tdd": {
       "description": "Test-driven development with red-green-refactor loop using vertical slices. Use for features (epic tasks) or bugs (specs/bugs/BUG-*.md).",
-      "sha256": "8a232210dc2c11d3",
+      "sha256": "d2f0ea62e87d3e2e",
       "path": "develop-tdd/SKILL.md"
     },
     "diagnose-root": {
@@ -88,22 +88,22 @@
     },
     "dispatch-agents": {
       "description": "Dispatch multiple subagents in parallel on independent tasks. No waiting between them — all run concurrently. Use when tasks are truly decoupled and speed matters. Distinct from delegate-task (concurrent here, no inter-task review gate).",
-      "sha256": "20b59cb63d770279",
+      "sha256": "3216762b32a9bdef",
       "path": "dispatch-agents/SKILL.md"
     },
     "edit-document": {
       "description": "Edit and improve documents by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, restructure, or improve any document — including specs/ files, articles, READMEs, or technical writing.",
-      "sha256": "99a1ed618396b1fb",
+      "sha256": "c11067bf20047a66",
       "path": "edit-document/SKILL.md"
     },
     "elaborate-spec": {
       "description": "Refine a rough idea into a clear, detailed specification through dialogue. Does not produce code. Use when user has a vague idea, wants to think through a feature before planning, or needs to turn \"I want X\" into a concrete spec.",
-      "sha256": "9edc17057449444d",
+      "sha256": "07ea333703b590e6",
       "path": "elaborate-spec/SKILL.md"
     },
     "enforce-first": {
       "description": "Apply the F.I.R.S.T test quality rubric (Fast, Independent, Repeatable, Self-Validating, Timely) to a test suite or individual tests. Use when develop-tdd is writing tests, when test quality needs to be checked, or when user mentions F.I.R.S.T or \"test quality\".",
-      "sha256": "cafd0bd664a74a2d",
+      "sha256": "83c74d2f427ddce1",
       "path": "enforce-first/SKILL.md"
     },
     "evolve-skill": {
@@ -113,57 +113,57 @@
     },
     "execute-plan": {
       "description": "Batch-execute tasks from the active epic capsule sequentially, with a human checkpoint after each step. Use when user has an approved plan and wants step-by-step oversight.",
-      "sha256": "844f2a3069f75f30",
+      "sha256": "3edebb0b38095f22",
       "path": "execute-plan/SKILL.md"
     },
     "extract-design": {
       "description": "\"Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose. Use when the user has an HTML prototype and wants a DESIGN.md to anchor their project's visual identity, or when seed-conventions has just scaffolded a new project.\"",
-      "sha256": "70fc3bc315b10b80",
+      "sha256": "633b765b44f0f7c0",
       "path": "extract-design/SKILL.md"
     },
     "fix-bug": {
       "description": "Bug fix orchestrator — active_flow fix_bug; reads specs/bugs/BUG-*.md; chains investigate-bug, develop-tdd, validate-fix. Use when user reports a defect.",
-      "sha256": "aa6fe406ba87a648",
+      "sha256": "ee022abfdad4681c",
       "path": "fix-bug/SKILL.md"
     },
     "grill-me": {
       "description": "Interactive assumption-surfacing Q&A that stress-tests a plan through relentless questioning until every decision is resolved. Use when user wants to challenge a plan, validate decisions from conversation/context, or mentions \"grill me\". For doc-grounded variant, use grill-with-docs.",
-      "sha256": "8456e38dfee44939",
+      "sha256": "2372d88ab66b1393",
       "path": "grill-me/SKILL.md"
     },
     "grill-with-docs": {
       "description": "Doc-grounded variant of grill-me — stress-tests plan assumptions by fetching and citing real library or API documentation. Every challenge must cite a real URL. Use when the plan depends on a specific library or external API.",
-      "sha256": "8ea5ebc5cc2d3434",
+      "sha256": "66e9e2725d3d95e9",
       "path": "grill-with-docs/SKILL.md"
     },
     "guard-git": {
       "description": "Block dangerous git commands (push, force push, reset --hard, clean, branch -D, checkout/restore .) and enforce Conventional Commits & Branch Protection before an AI agent runs them. Installs hook scripts for Claude Code, Cursor, Cursor CLI, and Gemini CLI; documents Google Antigravity Terminal deny lists. Use when the user wants git safety hooks, to block git push or destructive git in agents, or to mirror the same policy across AI coding tools.",
-      "sha256": "714da72cbb85a255",
+      "sha256": "52f6b9c61c89ee23",
       "path": "guard-git/SKILL.md"
     },
     "hook-commits": {
       "description": "Set up pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.",
-      "sha256": "bb6fac42390670c5",
+      "sha256": "f00ab1c07ecd774e",
       "path": "hook-commits/SKILL.md"
     },
     "inspect-quality": {
       "description": "Interactive QA session where user reports bugs or issues conversationally, and the agent logs them to specs/bugs/registry.yaml with a structured audit schema. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, or mentions \"QA session\".",
-      "sha256": "de13d11018beab6a",
+      "sha256": "f7652e1233f12fdf",
       "path": "inspect-quality/SKILL.md"
     },
     "investigate-bug": {
       "description": "Investigate a bug or issue by exploring the codebase to find root cause, then write a TDD-based fix plan to specs/bugs/BUG-*.md. Use when user reports a bug, wants to investigate a problem, mentions \"triage\", or wants to plan a fix.",
-      "sha256": "46e956e627f24b46",
+      "sha256": "cbe70afedfe883bc",
       "path": "investigate-bug/SKILL.md"
     },
     "kickoff-branch": {
       "description": "Create a git worktree and feature branch, then verify a clean test baseline before any code is written. Use when starting a new feature or task, when user wants to work in isolation from main, or mentions \"start a branch\" or \"new worktree\".",
-      "sha256": "d3c74c05a8d790c0",
+      "sha256": "2ff4f9e288347945",
       "path": "kickoff-branch/SKILL.md"
     },
     "map-codebase": {
       "description": "\"Derives the tech-stack doc from scratch by scanning the codebase — analyzes stack, architecture, and gray areas (error handling, API shapes) and persists findings into specs/tech-architecture/tech-stack.md. Run when the tech doc doesn't exist yet; use survey-context to consume it once it does.\"",
-      "sha256": "0ff035d8f8baf4f8",
+      "sha256": "020fe6bf49127625",
       "path": "map-codebase/SKILL.md"
     },
     "migrate-spec": {
@@ -173,22 +173,22 @@
     },
     "model-domain": {
       "description": "Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates specs/tech-architecture/tech-stack.md and specs/adr/ inline as decisions crystallise. Use when user wants to stress-test a plan against their project's domain language and documented decisions.",
-      "sha256": "9cdd34fc9952d06b",
+      "sha256": "311658f86e28e585",
       "path": "model-domain/SKILL.md"
     },
     "orchestrate-project": {
       "description": "Meta-skill that enforces the 6-phase core loop (discover → elaborate → plan → build → verify → release) with hard gates. Use to coordinate multi-phase projects with guaranteed quality checkpoints. One-time command for the entire project lifecycle.",
-      "sha256": "542276f88198ae72",
+      "sha256": "1b5002196dd4800b",
       "path": "orchestrate-project/SKILL.md"
     },
     "organize-workspace": {
       "description": "Scans the active workspace for disposable artifacts—logs, caches, stale build output, and stray draft markdown—and proposes consolidation of scattered assets. Produces a reviewable list, asks for explicit confirmation before any delete or move, and optionally revises .gitignore. Use when the user says \"clean my room\", \"organize workspace\", \"workspace cleanup\", \"remove temp files\", \"organize assets\", \"gitignore\", or wants a safe tidy pass.",
-      "sha256": "1595876ed98943d5",
+      "sha256": "f010d1af95b681d7",
       "path": "organize-workspace/SKILL.md"
     },
     "plan-refactor": {
       "description": "Create a detailed refactor plan with tiny commits via user interview, then save it as specs/REFACTOR_LATEST.md. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.",
-      "sha256": "2785dc22454f0104",
+      "sha256": "f18e2058d2ded6a5",
       "path": "plan-refactor/SKILL.md"
     },
     "plan-release": {
@@ -198,7 +198,7 @@
     },
     "plan-work": {
       "description": "\"PLANNING SPINE STEP 3 of 3 — Plan the work: write detailed implementation tasks into the active epic capsule (specs/epics/eNN-slug/). Produces countable-story-format .md specs and runnable -tasks.yaml files. Use after slice-tasks (step 2). Not a substitute for scope-work (step 1) or slice-tasks (step 2).\"",
-      "sha256": "30a021b06af25f08",
+      "sha256": "9b94a9eef2c6b861",
       "path": "plan-work/SKILL.md"
     },
     "publish-package": {
@@ -208,17 +208,17 @@
     },
     "quick-fix": {
       "description": "\"Streamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger.\"",
-      "sha256": "2b9f1cd6557b6256",
+      "sha256": "455e91c94295eac9",
       "path": "quick-fix/SKILL.md"
     },
     "release-branch": {
       "description": "Make the merge/PR/keep/discard decision for a feature branch, verify coverage gates, create the PR with gh, and clean up the worktree. Use when a feature is done and ready to ship, or when user says \"release\", \"merge\", or \"open a PR\".",
-      "sha256": "0514cbd9163e4e87",
+      "sha256": "9b36d5324807fe61",
       "path": "release-branch/SKILL.md"
     },
     "request-review": {
       "description": "Dispatch a fresh reviewer agent with a clean context to critique the code after audit-code passes. The reviewer has no shared state with the coding agent and gives a genuine second opinion. Use after audit-code passes, before committing, or when user wants an independent code review.",
-      "sha256": "b2498ecdf55104b6",
+      "sha256": "6dd1eb3856926184",
       "path": "request-review/SKILL.md"
     },
     "research-first": {
@@ -228,12 +228,12 @@
     },
     "reset-baseline": {
       "description": "Restore the project to a known clean state between agent runs or experiments. Use between benchmark runs, after a failed spike, or when user wants a clean working tree.",
-      "sha256": "d0b3ee9d9c292334",
+      "sha256": "eca0e748af2ce42a",
       "path": "reset-baseline/SKILL.md"
     },
     "respond-review": {
       "description": "Act on a reviewer agent's feedback systematically — categorize findings, apply fixes, verify tests still pass. Use after request-review returns a report, or when user wants to work through code review findings.",
-      "sha256": "c16bbe4854a0d665",
+      "sha256": "6e5980ef2cf9ccac",
       "path": "respond-review/SKILL.md"
     },
     "run-benchmark": {
@@ -263,12 +263,12 @@
     },
     "security-review": {
       "description": "> AI-powered security analysis of code changes — traces data flow, detects injection, auth bypass, secrets exposure, and unsafe deserialization across files. Use when reviewing pending changes, before release-branch, during verify-work Phase 5, during build-epic Step 0 threat modeling, or when the user says \"security review\" or \"scan for vulns\".",
-      "sha256": "8fe9fa518af2aaa6",
+      "sha256": "9e57715a2a0b58ab",
       "path": "security-review/SKILL.md"
     },
     "seed-conventions": {
       "description": "Generate CLAUDE.md and CONVENTIONS.md for a brand-new project through a brief interview, and create the specs/ directory with evolved bigpowers structure (product/, tech-architecture/, verifications/, epics/archive/). Entry point for greenfield projects. Use when starting a new project from scratch, when user asks to set up AI agent conventions, or when there is no CLAUDE.md yet.",
-      "sha256": "cd3a7fc52d1b0035",
+      "sha256": "9b78d7d47df46888",
       "path": "seed-conventions/SKILL.md"
     },
     "session-state": {
@@ -278,12 +278,12 @@
     },
     "setup-environment": {
       "description": "Pre-install dependencies and configure tools before development work begins. Use at session start on a fresh clone, before kickoff-branch, or when user says setup environment or install deps.",
-      "sha256": "3092662402943645",
+      "sha256": "a5684353acc28aa8",
       "path": "setup-environment/SKILL.md"
     },
     "simulate-agents": {
       "description": "Run Mock User and Auditor agents against a feature in fresh contexts before human review. Use after verify-work, before request-review, when user wants pre-review simulation.",
-      "sha256": "4ce3c2fa40ae43e9",
+      "sha256": "01da249685a5c811",
       "path": "simulate-agents/SKILL.md"
     },
     "slice-tasks": {
@@ -293,12 +293,12 @@
     },
     "smoke-test": {
       "description": "\"Post-deploy health-check against a live URL. Validates HTTP status, response content, and critical endpoints. Runnable standalone OR as the final step of the deploy skill.\"",
-      "sha256": "85d2de9e87e141f7",
+      "sha256": "f9a106b47a08dce4",
       "path": "smoke-test/SKILL.md"
     },
     "spike-prototype": {
       "description": "Throw-away prototype for unknown problem spaces. Output is learning notes in specs/archive/spikes/SPIKE-<name>.md, not production code. Use when the domain or technology is unexplored, when estimates are impossible without experimentation, or when user says \"spike\", \"prototype\", or \"proof of concept\".",
-      "sha256": "568e52ae1e3a9213",
+      "sha256": "291529ae21ff981b",
       "path": "spike-prototype/SKILL.md"
     },
     "stocktake-skills": {
@@ -313,7 +313,7 @@
     },
     "terse-mode": {
       "description": "Fallback ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use ONLY when context is critically long and compressing output is necessary to continue. Not a strategy — token discipline comes from code shape (small functions, unique names, headless tests), not terser prompts. Use when user says \"caveman mode\", \"terse mode\", \"less tokens\", \"be brief\", or invokes /terse-mode.",
-      "sha256": "d46f9b0fc252e468",
+      "sha256": "36e398659ef88f32",
       "path": "terse-mode/SKILL.md"
     },
     "trace-requirement": {
@@ -323,22 +323,22 @@
     },
     "using-bigpowers": {
       "description": "One-time bootstrap that introduces the bigpowers skills system, the PMBOK lifecycle arc, and tells you which skill to call first for your situation. Use when starting with bigpowers for the first time, when user asks \"where do I start?\", or when the skills system needs to be explained.",
-      "sha256": "3e73bdd359b49743",
+      "sha256": "172d9f3f4c0b3b96",
       "path": "using-bigpowers/SKILL.md"
     },
     "validate-contracts": {
       "description": "\"Assert data shape consistency across system boundaries — live API responses against JSON Schema, key-set comparison across layers, data shape validation for migrations and exports. Catches silent data corruption before deploy.\"",
-      "sha256": "59cf618f642fa10c",
+      "sha256": "dbdae60ae8d6ce70",
       "path": "validate-contracts/SKILL.md"
     },
     "validate-fix": {
       "description": "Prove a fix works before declaring done — re-run the failing test, run the full suite, typecheck, lint, and harden against recurrence. Use after implementing a bug fix, when user says \"is this fixed?\", or before closing an investigation.",
-      "sha256": "f559f4b8dcf03c4a",
+      "sha256": "1bf728d7dee1b3b5",
       "path": "validate-fix/SKILL.md"
     },
     "verify-work": {
       "description": "Multi-phase UAT gate — cold-start smoke, build, typecheck, lint, tests, step-by-step manual verification, gaps-closure loop. Use after execute-plan or develop-tdd, before audit-code.",
-      "sha256": "7ea4ccf0ed1303fb",
+      "sha256": "826507cd3e4242af",
       "path": "verify-work/SKILL.md"
     },
     "visual-dashboard": {
@@ -353,7 +353,7 @@
     },
     "wire-observability": {
       "description": "Add structured JSON logging, observability commands, and idempotent setup scripts to a project. Use when a project needs production-readiness instrumentation, when user wants structured logging, or as a production-readiness gate at any phase of development.",
-      "sha256": "01e751c37dab47b3",
+      "sha256": "ad4696522f529530",
       "path": "wire-observability/SKILL.md"
     },
     "write-document": {

package/smoke-test/SKILL.md

@@ -64,3 +64,7 @@ The `deploy` skill references `smoke-test` as its final verification step:
 # In deploy workflow — after successful deploy
 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"`

package/spike-prototype/SKILL.md

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

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