bigpowers 2.45.0 → 2.45.2

package/skills/seed-conventions/SKILL.md

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

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

package/skills/spike-prototype/SKILL.md

@@ -94,6 +94,3 @@ After writing the findings, delete or discard the spike code. It is not meant to
 
 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/skills/terse-mode/SKILL.md

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

@@ -105,6 +105,3 @@ Start the HTTP dashboard with `visual-dashboard` → `GET /api/status?projectDir
 
 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/skills/validate-contracts/SKILL.md

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

package/skills/validate-fix/SKILL.md

@@ -103,6 +103,3 @@ Mechanical verification (tests passing) is only half the fix. You must prove **b
 
 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/skills/wire-observability/SKILL.md

@@ -92,6 +92,3 @@ Place setup scripts in `scripts/setup.sh` (or language-appropriate equivalent).
 - [ ] 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/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": "6d76f83d71c5bd27",
+      "sha256": "0b9f702bffce874c",
       "path": "skills/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": "0d07d2fca30c1f2d",
+      "sha256": "0092965cd95bbec4",
       "path": "skills/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": "27128c418f7e546c",
+      "sha256": "2eed75737c24a772",
       "path": "skills/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": "4272ff777f9f43de",
+      "sha256": "36eeb9dbfe8c82c6",
       "path": "skills/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": "8660de5647b77bd8",
+      "sha256": "3d3a89525aefe19f",
       "path": "skills/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": "6f483d1c366613f3",
+      "sha256": "ec5f1565fd9299a1",
       "path": "skills/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": "6cead64f3b818922",
+      "sha256": "d527a2325d207d0a",
       "path": "skills/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": "21353242357ce913",
+      "sha256": "5b1950486cbaa75f",
       "path": "skills/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": "95c1ccce9af5dfd0",
+      "sha256": "299ab7e43f6d34df",
       "path": "skills/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": "9c62a42e064f5c04",
+      "sha256": "818ee25d49936aeb",
       "path": "skills/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": "f9f88fc01371f648",
+      "sha256": "b1d82bd4fcac1c22",
       "path": "skills/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": "d2f0ea62e87d3e2e",
+      "sha256": "b7ca497f1f4cba57",
       "path": "skills/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": "3216762b32a9bdef",
+      "sha256": "2d548860733f999c",
       "path": "skills/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": "c11067bf20047a66",
+      "sha256": "e844fb2203f3c2cd",
       "path": "skills/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": "07ea333703b590e6",
+      "sha256": "a7d79bc857cbc991",
       "path": "skills/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": "83c74d2f427ddce1",
+      "sha256": "285c7adf6490994c",
       "path": "skills/enforce-first/SKILL.md"
     },
     "evolve-skill": {
@@ -113,12 +113,12 @@
     },
     "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": "3edebb0b38095f22",
+      "sha256": "d32465c96632c375",
       "path": "skills/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": "633b765b44f0f7c0",
+      "sha256": "fd430693f333d97f",
       "path": "skills/extract-design/SKILL.md"
     },
     "fix-bug": {
@@ -128,7 +128,7 @@
     },
     "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": "2372d88ab66b1393",
+      "sha256": "0a7c14046a475feb",
       "path": "skills/grill-me/SKILL.md"
     },
     "grill-with-docs": {
@@ -138,32 +138,32 @@
     },
     "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": "52f6b9c61c89ee23",
+      "sha256": "7ed6b80ed376c4d1",
       "path": "skills/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": "f00ab1c07ecd774e",
+      "sha256": "c77cbbba45a26361",
       "path": "skills/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": "f7652e1233f12fdf",
+      "sha256": "cb76c2cbf3af8fbe",
       "path": "skills/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": "cbe70afedfe883bc",
+      "sha256": "e87c7ae746f084b6",
       "path": "skills/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": "2ff4f9e288347945",
+      "sha256": "8b499ee818c525e2",
       "path": "skills/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": "020fe6bf49127625",
+      "sha256": "13be4df4efe7df97",
       "path": "skills/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": "311658f86e28e585",
+      "sha256": "c84a93ca852ce68e",
       "path": "skills/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": "7bea8d8610e05ea7",
+      "sha256": "e18d418da4ec63e3",
       "path": "skills/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": "f010d1af95b681d7",
+      "sha256": "aad2c1c5f696cb51",
       "path": "skills/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": "f18e2058d2ded6a5",
+      "sha256": "0a1957ae7a8a79d5",
       "path": "skills/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": "9b94a9eef2c6b861",
+      "sha256": "2725a1a268255d15",
       "path": "skills/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": "911567fb4931943b",
+      "sha256": "57f1dcecf4d37006",
       "path": "skills/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": "9b36d5324807fe61",
+      "sha256": "d9df587d82f602fe",
       "path": "skills/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": "6dd1eb3856926184",
+      "sha256": "7ba12fa018b6633a",
       "path": "skills/request-review/SKILL.md"
     },
     "research-first": {
@@ -233,7 +233,7 @@
     },
     "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": "6e5980ef2cf9ccac",
+      "sha256": "51286ca777e529f0",
       "path": "skills/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": "9e57715a2a0b58ab",
+      "sha256": "568dbdb02da9fbd2",
       "path": "skills/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": "f67bb750533d826c",
+      "sha256": "0b6b6c07985b8a84",
       "path": "skills/seed-conventions/SKILL.md"
     },
     "session-state": {
@@ -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": "f9a106b47a08dce4",
+      "sha256": "af1aa794e9d8e430",
       "path": "skills/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": "291529ae21ff981b",
+      "sha256": "c595bbd61b207069",
       "path": "skills/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": "36e398659ef88f32",
+      "sha256": "e41fd895f27cca12",
       "path": "skills/terse-mode/SKILL.md"
     },
     "trace-requirement": {
@@ -323,17 +323,17 @@
     },
     "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": "532965a50772a04f",
+      "sha256": "9bdafc7e3c750c2d",
       "path": "skills/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": "dbdae60ae8d6ce70",
+      "sha256": "39b0a1cfa3a06c31",
       "path": "skills/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": "1bf728d7dee1b3b5",
+      "sha256": "5caa50c364da710b",
       "path": "skills/validate-fix/SKILL.md"
     },
     "verify-work": {
@@ -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": "ad4696522f529530",
+      "sha256": "773d8c07c585e0b3",
       "path": "skills/wire-observability/SKILL.md"
     },
     "write-document": {