bigpowers 2.50.0 → 2.51.0

package/skills/seed-conventions/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: seed-conventions
 model: sonnet
+effort: standard
 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.
 ---
 

package/skills/session-state/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: session-state
 model: haiku
+effort: standard
 description: Track implementation decisions and progress in specs/state.yaml to prevent context rot. Use at the start of a session to load context, and whenever a significant decision is made or a milestone is reached.
 ---
 
@@ -10,6 +11,8 @@ description: Track implementation decisions and progress in specs/state.yaml to
 
 Track the current state of implementation, including decisions made, pending tasks, and open questions, to ensure continuity across session boundaries and prevent "context rot."
 
+Session-state implements the **isolate** strategy from the context-engineering framework (docs/references/context-engineering.md): each agent gets exactly the context it needs — no more — by recording decisions so the next agent can cold-start without replaying history. The four strategies (write, select, compress, isolate) work together: session-state handles isolation, terse-mode handles compression, survey-context handles selection, and CONVENTIONS.md ensures token-efficient writing.
+
 ## Goal
 
 Maintain a single source of truth for the *current* session in `specs/state.yaml`. This complements long-term docs in `specs/tech-architecture/` and delivery detail in `specs/epics/` + `specs/release-plan.yaml`.

package/skills/setup-environment/SKILL.md

@@ -2,6 +2,7 @@
 name: 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.
 model: haiku
+effort: standard
 ---
 
 # Setup Environment

package/skills/simulate-agents/SKILL.md

@@ -2,6 +2,7 @@
 name: 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.
 model: sonnet
+effort: standard
 ---
 
 # Simulate Agents

package/skills/slice-tasks/SKILL.md

@@ -2,6 +2,7 @@
 name: slice-tasks
 description: "PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work."
 model: sonnet
+effort: standard
 ---
 
 # Slice Tasks

package/skills/smoke-test/SKILL.md

@@ -2,6 +2,7 @@
 name: 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."
 model: sonnet
+effort: standard
 ---
 
 # Smoke Test

package/skills/spike-prototype/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: spike-prototype
 model: sonnet
+effort: standard
 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".
 ---
 

package/skills/stocktake-skills/SKILL.md

@@ -2,6 +2,7 @@
 name: stocktake-skills
 description: Sequential subagent batch audit of the bigpowers skill catalog — Quick Scan (changed only) or Full (all skills). Use during sustain phase, before a major release, or when catalog drift is suspected.
 model: sonnet
+effort: standard
 ---
 
 # Stocktake Skills

package/skills/survey-context/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: survey-context
 model: haiku
+effort: standard
 description: Per-task context bootstrap — reads existing specs/ and tech-architecture docs to map the current lifecycle phase and suggest the next skill. Use at the start of any task, when returning after a break, or when unsure what to do next. For deriving a tech-stack doc from scratch, use map-codebase first.
 ---
 
@@ -114,7 +115,7 @@ Report blockers first, before recommendations.
 
 ### 8. Record story start timestamp
 
-At story start, write `metrics.story_start` with the current ISO 8601 timestamp to `specs/state.yaml` for cycle-time tracking.
+At story start, write `metrics.story_start` with the current ISO 8601 timestamp to `specs/state.yaml` as an **informational progress marker only** — not a measurement input. Cycle-time metrics are now derived from git commit history via `scripts/record-cycle-time.sh` (see `skills/release-branch/REFERENCE.md` §Cycle-time recording).
 
 ## Utility outputs
 

package/skills/terse-mode/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: terse-mode
 model: haiku
+effort: standard
 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.
 ---
 

package/skills/trace-requirement/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: trace-requirement
 model: haiku
+effort: standard
 description: Link story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests. Produces specs/TRACEABILITY_LATEST.md. Use when you want to verify coverage of a release plan, audit which stories are implemented, or find "dark" stories with no code.
 ---
 

package/skills/using-bigpowers/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: using-bigpowers
 model: sonnet
+effort: standard
 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.
 ---
 

package/skills/validate-contracts/SKILL.md

@@ -2,6 +2,7 @@
 name: 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."
 model: sonnet
+effort: standard
 ---
 
 # Validate Contracts

package/skills/validate-fix/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: validate-fix
 model: haiku
+effort: standard
 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.
 ---
 

package/skills/verify-work/SKILL.md

@@ -2,6 +2,7 @@
 name: 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.
 model: haiku
+effort: standard
 ---
 
 # Verify Work

package/skills/visual-dashboard/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: visual-dashboard
 model: sonnet
+effort: standard
 description: Start a browser-based dashboard that visualizes architecture, implementation plans, and project status. Persists artifacts in .bigpowers/dashboard/. Reads specs/state.yaml, release-plan.yaml, epics, and planning-status via HTTP API or opencode panel.
 ---
 

package/skills/wire-ci/SKILL.md

@@ -2,6 +2,7 @@
 name: wire-ci
 description: "CI pipeline setup with pre-built templates and local validation. Generates GitHub Actions workflows, validates YAML syntax and permissions, supports dry-run via act/gh. The CI equivalent of wire-observability."
 model: sonnet
+effort: standard
 ---
 
 # Wire CI

package/skills/wire-observability/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: wire-observability
 model: sonnet
+effort: standard
 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.
 ---
 

package/skills/write-document/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: write-document
 model: sonnet
+effort: standard
 description: Write, organize, and sync high-integrity technical documents using the BMAD methodology. Ensures every document is Bold, Minimal, Actionable, and Durable. Use when creating architectural docs, technical guides, or organizing the specs/ directory.
 ---