bigpowers 2.88.11 → 2.88.13

package/.opencode/skills/migrate-spec/SKILL.md

@@ -4,12 +4,12 @@ model: sonnet
 description: "Detect GSD, spec-kit, or BMAD spec artifacts and transform them into bigpowers YAML layout (state.yaml, release-plan.yaml, epics/, requirements/, plans/, ADRs). Use when migrating foreign spec docs."
 ---
 
-# story: e25s01
-# story: e25s02
-# story: e25s03
-# story: e25s04
-# story: e25s05
-# story: e25s06
+<!-- story: e25s01 -->
+<!-- story: e25s02 -->
+<!-- story: e25s03 -->
+<!-- story: e25s04 -->
+<!-- story: e25s05 -->
+<!-- story: e25s06 -->
 
 # Migrate Spec
 

package/.opencode/skills/plan-work/SKILL.md

@@ -4,7 +4,7 @@ model: opus
 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)."
 ---
 
-# story: e45s29
+<!-- story: e45s29 -->
 
 # Plan Work
 

package/.opencode/skills/request-review/SKILL.md

@@ -4,12 +4,23 @@ model: opus
 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."
 ---
 
-# story: e45s28
+<!-- story: e45s28 -->
 
 # Request Review
 
 Dispatch fresh reviewer agents with clean contexts. Reviewers have no shared state — they find what the coding agent missed.
 
+## Target (argument)
+
+If an argument was passed after `/request-review` (e.g. `/request-review abc1234` or `/request-review HEAD~3..HEAD`), use it as the diff target when building the reviewer brief:
+
+```bash
+git diff <arg>        # range: abc..def, HEAD~3..HEAD
+git show <arg>        # single commit: abc1234
+```
+
+If no argument was given, review uncommitted working-tree changes.
+
 **Distinct from `audit-code`:** `audit-code` is self-review (internal). This skill dispatches external agents.
 
 **Solo developer note:** Reviewer agents replace the human reviewer.

package/.opencode/skills/research-first/SKILL.md

@@ -4,8 +4,8 @@ model: sonnet
 description: "Look-before-build — search registries, repo, existing skills, and web for prior art before implementing. Appends Prior Art to the spec. Use after survey-context and before elaborate-spec, when adding dependencies, or when the task may already be solved."
 ---
 
-# story: e03s01
-# story: e21s02
+<!-- story: e03s01 -->
+<!-- story: e21s02 -->
 
 # Research First
 

package/.opencode/skills/run-planning/SKILL.md

@@ -4,7 +4,7 @@ model: sonnet
 description: "DISCOVER-PHASE ADVANCER — Drive the discover-phase checklist (specs/planning-status.yaml) through survey-context → scope-work → research-first → elaborate-spec → plan-release → slice-tasks. NOT a duplicate of plan-work or the planning spine; it orchestrates the pre-coding discover phase only."
 ---
 
-# story: e24s03
+<!-- story: e24s03 -->
 
 # Run Planning
 

package/.opencode/skills/scope-work/SKILL.md

@@ -4,8 +4,8 @@ model: sonnet
 description: "PLANNING SPINE STEP 1 of 3 — Scope the work: define what is in and out of scope and save as specs/product/SCOPE_LATEST.yaml. Use before slice-tasks or plan-release on any new initiative. Not a substitute for slice-tasks (step 2) or plan-work (step 3)."
 ---
 
-# story: e03s01
-# story: e24s02
+<!-- story: e03s01 -->
+<!-- story: e24s02 -->
 
 # Scope Work
 

package/.opencode/skills/search-skills/SKILL.md

@@ -4,8 +4,8 @@ model: haiku
 description: "Find the right bigpowers skill from natural-language intent using a local lexical index over SKILL.md frontmatter. Use when unsure which skill to invoke, or at start of research-first."
 ---
 
-# story: e09s01
-# story: e21s01
+<!-- story: e09s01 -->
+<!-- story: e21s01 -->
 
 # Search Skills
 

package/.opencode/skills/security-review/SKILL.md

@@ -4,16 +4,16 @@ model: sonnet
 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\"."
 ---
 
-# story: e45s41
+<!-- story: e45s41 -->
 <!-- story: e45s18 -->
-# story: e26s01
-# story: e26s02
-# story: e26s03
-# story: e26s04
-# story: e26s05
-# story: e26s06
-# story: e26s07
-# story: e45s26
+<!-- story: e26s01 -->
+<!-- story: e26s02 -->
+<!-- story: e26s03 -->
+<!-- story: e26s04 -->
+<!-- story: e26s05 -->
+<!-- story: e26s06 -->
+<!-- story: e26s07 -->
+<!-- story: e45s26 -->
 
 # Security Review
 

package/.opencode/skills/seed-conventions/SKILL.md

@@ -4,12 +4,12 @@ model: sonnet
 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."
 ---
 
-# story: e10s01
-# story: e47s02
-# story: e10s02
-# story: e51s02
-# story: e45s21
-# story: e79s03
+<!-- story: e10s01 -->
+<!-- story: e47s02 -->
+<!-- story: e10s02 -->
+<!-- story: e51s02 -->
+<!-- story: e45s21 -->
+<!-- story: e79s03 -->
 
 
 # Seed Conventions

package/.opencode/skills/session-state/SKILL.md

@@ -4,7 +4,7 @@ model: haiku
 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."
 ---
 
-# story: e45s23
+<!-- story: e45s23 -->
 
 # Session State
 > **HARD GATE** — **HARD GATE** — Session state must be synchronized with git state. If state.yaml conflicts with the working tree, halt and ask for clarification. Do NOT assume state is correct.

package/.opencode/skills/slice-tasks/SKILL.md

@@ -4,7 +4,7 @@ model: sonnet
 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."
 ---
 
-# story: e45s29
+<!-- story: e45s29 -->
 
 # Slice Tasks
 

package/.opencode/skills/stocktake-skills/SKILL.md

@@ -4,7 +4,7 @@ model: sonnet
 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."
 ---
 
-# story: e09s01
+<!-- story: e09s01 -->
 <!-- story: e45s12 -->
 <!-- story: e79s04 -->
 

package/.opencode/skills/survey-context/SKILL.md

@@ -4,7 +4,7 @@ model: haiku
 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."
 ---
 
-# story: e82s02
+<!-- story: e82s02 -->
 
 # Survey Context
 

package/.pi/package.json

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

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

@@ -4,8 +4,18 @@ description: "Self-review checklist for the coding agent to run before dispatchi
 ---
 
 # Audit Code
-> **HARD GATE** — **HARD GATE** — Audit must check for: bugs (correctness), security, performance, and clarity. Do NOT skip security review if the code touches user data, auth, or external APIs.
+> **HARD GATE** — Audit must check for: bugs (correctness), security, performance, and clarity. Do NOT skip security review if the code touches user data, auth, or external APIs.
 
+## Target (argument)
+
+If an argument was passed after `/audit` (e.g. `/audit abc1234` or `/audit HEAD~3..HEAD`), use it as the diff target:
+
+```bash
+git diff <arg>        # range or two-ref form: abc..def, HEAD~3..HEAD
+git show <arg>        # single commit: abc1234
+```
+
+If no argument was given, review uncommitted working-tree changes (`git diff` + `git diff --staged`).
 
 Run this self-review before asking anyone else to look at the code. The goal is to catch everything that is clearly wrong or missing — so the reviewer can focus on design and architecture, not hygiene.
 
@@ -32,7 +42,6 @@ Apply the full checklist to churn-ranked files in descending order. Files with z
 bash scripts/lib/parallel-review-worktrees.sh audit-code
 ```
 
-
 ## Checklist
 
 ### Supply Chain & Security
@@ -131,7 +140,6 @@ In `--gate` mode, print one summary line per checklist section (`PASS Supply Cha
 Gate: READY -> next: commit-message
 Writes: state.yaml handoff.next_skill = commit-message
 
-
 <!-- story: e01s02 -->
 <!-- story: e06s03 -->
 <!-- story: e07s01 -->

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

@@ -3,7 +3,7 @@ name: 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."
 ---
 
-# story: e20s05
+<!-- story: e20s05 -->
 
 # Build Epic
 

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

@@ -3,8 +3,8 @@ name: change-request
 description: "Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization."
 ---
 
-# story: e45s29
-# story: e20s01
+<!-- story: e45s29 -->
+<!-- story: e20s01 -->
 
 # Change Request
 

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

@@ -3,7 +3,7 @@ name: 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."
 ---
 
-# story: e82s02
+<!-- story: e82s02 -->
 
 # Commit Message
 > **HARD GATE** — **HARD GATE** — Commits must follow Conventional Commits spec (type(scope): description). Do NOT use vague messages like 'fix' or 'updates.' The message must explain the 'why,' not the 'what.'

package/.pi/prompts/compose-workflow.md

@@ -3,9 +3,9 @@ name: compose-workflow
 description: "Chain multiple bigpowers skills into a custom workflow recipe saved in specs/. Use when a project repeats a non-standard skill sequence, or user wants a documented playbook beyond orchestrate-project modes."
 ---
 
-# story: e09s01
-# story: e45s27
-# story: e21s04
+<!-- story: e09s01 -->
+<!-- story: e45s27 -->
+<!-- story: e21s04 -->
 
 # Compose Workflow
 > **HARD GATE** — **HARD GATE** — Workflows are orchestration, not automation. Do NOT create workflows for tasks that should be single skills. Workflow complexity must be justified.

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

@@ -3,7 +3,7 @@ name: 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)."
 ---
 
-# story: e45s30
+<!-- story: e45s30 -->
 
 # Delegate Task
 > **HARD GATE** — **HARD GATE** — Delegated work must have clear success criteria and verification commands. The delegate must be able to verify completion independently.

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

@@ -3,12 +3,12 @@ name: 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)."
 ---
 
-# story: e09s04
-# story: e45s38
+<!-- story: e09s04 -->
+<!-- story: e45s38 -->
 <!-- story: e45s11 -->
 
 
-# story: e45s30
+<!-- story: e45s30 -->
 
 # Dispatch Agents
 > **HARD GATE** — **HARD GATE** — Agent work must be parallelizable and have explicit synchronization points. Do NOT dispatch work that has hidden dependencies between agents.

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

@@ -3,10 +3,10 @@ name: evolve-skill
 description: "Benchmark-gated skill evolution — consume bigpowers-benchmark report, propose plan-work change, edit skill via craft-skill, re-run benchmark, record ADR. Use when a skill underperforms on benchmark or stocktake finds systemic gap."
 ---
 
-# story: e23s03
+<!-- story: e23s03 -->
 
-# story: e09s01
-# story: e09s05
+<!-- story: e09s01 -->
+<!-- story: e09s05 -->
 
 # Evolve Skill
 

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

@@ -3,9 +3,9 @@ name: kickoff-branch
 description: "Create an isolated Git worktree/branch or Jujutsu workspace, then verify a clean test baseline before code. Use when starting a feature or task."
 ---
 
-# story: e51s03
-# story: e20s03
-# story: e82s02
+<!-- story: e51s03 -->
+<!-- story: e20s03 -->
+<!-- story: e82s02 -->
 
 
 # Kickoff Branch

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

@@ -3,12 +3,12 @@ name: migrate-spec
 description: "Detect GSD, spec-kit, or BMAD spec artifacts and transform them into bigpowers YAML layout (state.yaml, release-plan.yaml, epics/, requirements/, plans/, ADRs). Use when migrating foreign spec docs."
 ---
 
-# story: e25s01
-# story: e25s02
-# story: e25s03
-# story: e25s04
-# story: e25s05
-# story: e25s06
+<!-- story: e25s01 -->
+<!-- story: e25s02 -->
+<!-- story: e25s03 -->
+<!-- story: e25s04 -->
+<!-- story: e25s05 -->
+<!-- story: e25s06 -->
 
 # Migrate Spec
 

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

@@ -3,7 +3,7 @@ name: 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)."
 ---
 
-# story: e45s29
+<!-- story: e45s29 -->
 
 # Plan Work
 

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

@@ -3,12 +3,23 @@ name: 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."
 ---
 
-# story: e45s28
+<!-- story: e45s28 -->
 
 # Request Review
 
 Dispatch fresh reviewer agents with clean contexts. Reviewers have no shared state — they find what the coding agent missed.
 
+## Target (argument)
+
+If an argument was passed after `/request-review` (e.g. `/request-review abc1234` or `/request-review HEAD~3..HEAD`), use it as the diff target when building the reviewer brief:
+
+```bash
+git diff <arg>        # range: abc..def, HEAD~3..HEAD
+git show <arg>        # single commit: abc1234
+```
+
+If no argument was given, review uncommitted working-tree changes.
+
 **Distinct from `audit-code`:** `audit-code` is self-review (internal). This skill dispatches external agents.
 
 **Solo developer note:** Reviewer agents replace the human reviewer.

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

@@ -3,8 +3,8 @@ name: research-first
 description: "Look-before-build — search registries, repo, existing skills, and web for prior art before implementing. Appends Prior Art to the spec. Use after survey-context and before elaborate-spec, when adding dependencies, or when the task may already be solved."
 ---
 
-# story: e03s01
-# story: e21s02
+<!-- story: e03s01 -->
+<!-- story: e21s02 -->
 
 # Research First
 

package/.pi/prompts/run-planning.md

@@ -3,7 +3,7 @@ name: run-planning
 description: "DISCOVER-PHASE ADVANCER — Drive the discover-phase checklist (specs/planning-status.yaml) through survey-context → scope-work → research-first → elaborate-spec → plan-release → slice-tasks. NOT a duplicate of plan-work or the planning spine; it orchestrates the pre-coding discover phase only."
 ---
 
-# story: e24s03
+<!-- story: e24s03 -->
 
 # Run Planning
 

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

@@ -3,8 +3,8 @@ name: scope-work
 description: "PLANNING SPINE STEP 1 of 3 — Scope the work: define what is in and out of scope and save as specs/product/SCOPE_LATEST.yaml. Use before slice-tasks or plan-release on any new initiative. Not a substitute for slice-tasks (step 2) or plan-work (step 3)."
 ---
 
-# story: e03s01
-# story: e24s02
+<!-- story: e03s01 -->
+<!-- story: e24s02 -->
 
 # Scope Work
 

package/.pi/prompts/search-skills.md

@@ -3,8 +3,8 @@ name: search-skills
 description: "Find the right bigpowers skill from natural-language intent using a local lexical index over SKILL.md frontmatter. Use when unsure which skill to invoke, or at start of research-first."
 ---
 
-# story: e09s01
-# story: e21s01
+<!-- story: e09s01 -->
+<!-- story: e21s01 -->
 
 # Search Skills
 

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

@@ -3,16 +3,16 @@ name: 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\"."
 ---
 
-# story: e45s41
+<!-- story: e45s41 -->
 <!-- story: e45s18 -->
-# story: e26s01
-# story: e26s02
-# story: e26s03
-# story: e26s04
-# story: e26s05
-# story: e26s06
-# story: e26s07
-# story: e45s26
+<!-- story: e26s01 -->
+<!-- story: e26s02 -->
+<!-- story: e26s03 -->
+<!-- story: e26s04 -->
+<!-- story: e26s05 -->
+<!-- story: e26s06 -->
+<!-- story: e26s07 -->
+<!-- story: e45s26 -->
 
 # Security Review
 

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

@@ -3,12 +3,12 @@ name: 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."
 ---
 
-# story: e10s01
-# story: e47s02
-# story: e10s02
-# story: e51s02
-# story: e45s21
-# story: e79s03
+<!-- story: e10s01 -->
+<!-- story: e47s02 -->
+<!-- story: e10s02 -->
+<!-- story: e51s02 -->
+<!-- story: e45s21 -->
+<!-- story: e79s03 -->
 
 
 # Seed Conventions

package/.pi/prompts/session-state.md

@@ -3,7 +3,7 @@ name: session-state
 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."
 ---
 
-# story: e45s23
+<!-- story: e45s23 -->
 
 # Session State
 > **HARD GATE** — **HARD GATE** — Session state must be synchronized with git state. If state.yaml conflicts with the working tree, halt and ask for clarification. Do NOT assume state is correct.

package/.pi/prompts/slice-tasks.md

@@ -3,7 +3,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."
 ---
 
-# story: e45s29
+<!-- story: e45s29 -->
 
 # Slice Tasks
 

package/.pi/prompts/stocktake-skills.md

@@ -3,7 +3,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."
 ---
 
-# story: e09s01
+<!-- story: e09s01 -->
 <!-- story: e45s12 -->
 <!-- story: e79s04 -->
 

package/.pi/prompts/survey-context.md

@@ -3,7 +3,7 @@ name: survey-context
 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."
 ---
 
-# story: e82s02
+<!-- story: e82s02 -->
 
 # Survey Context
 

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

@@ -5,8 +5,18 @@ description: "Self-review checklist for the coding agent to run before dispatchi
 ---
 
 # Audit Code
-> **HARD GATE** — **HARD GATE** — Audit must check for: bugs (correctness), security, performance, and clarity. Do NOT skip security review if the code touches user data, auth, or external APIs.
+> **HARD GATE** — Audit must check for: bugs (correctness), security, performance, and clarity. Do NOT skip security review if the code touches user data, auth, or external APIs.
 
+## Target (argument)
+
+If an argument was passed after `/audit` (e.g. `/audit abc1234` or `/audit HEAD~3..HEAD`), use it as the diff target:
+
+```bash
+git diff <arg>        # range or two-ref form: abc..def, HEAD~3..HEAD
+git show <arg>        # single commit: abc1234
+```
+
+If no argument was given, review uncommitted working-tree changes (`git diff` + `git diff --staged`).
 
 Run this self-review before asking anyone else to look at the code. The goal is to catch everything that is clearly wrong or missing — so the reviewer can focus on design and architecture, not hygiene.
 
@@ -33,7 +43,6 @@ Apply the full checklist to churn-ranked files in descending order. Files with z
 bash scripts/lib/parallel-review-worktrees.sh audit-code
 ```
 
-
 ## Checklist
 
 ### Supply Chain & Security
@@ -132,7 +141,6 @@ In `--gate` mode, print one summary line per checklist section (`PASS Supply Cha
 Gate: READY -> next: commit-message
 Writes: state.yaml handoff.next_skill = commit-message
 
-
 <!-- story: e01s02 -->
 <!-- story: e06s03 -->
 <!-- story: e07s01 -->

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

@@ -4,7 +4,7 @@ model: sonnet
 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."
 ---
 
-# story: e20s05
+<!-- story: e20s05 -->
 
 # Build Epic
 

package/.pi/skills/change-request/SKILL.md

@@ -4,8 +4,8 @@ model: sonnet
 description: "Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization."
 ---
 
-# story: e45s29
-# story: e20s01
+<!-- story: e45s29 -->
+<!-- story: e20s01 -->
 
 # Change Request
 

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

@@ -4,7 +4,7 @@ model: haiku
 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."
 ---
 
-# story: e82s02
+<!-- story: e82s02 -->
 
 # Commit Message
 > **HARD GATE** — **HARD GATE** — Commits must follow Conventional Commits spec (type(scope): description). Do NOT use vague messages like 'fix' or 'updates.' The message must explain the 'why,' not the 'what.'

package/.pi/skills/compose-workflow/SKILL.md

@@ -4,9 +4,9 @@ model: sonnet
 description: "Chain multiple bigpowers skills into a custom workflow recipe saved in specs/. Use when a project repeats a non-standard skill sequence, or user wants a documented playbook beyond orchestrate-project modes."
 ---
 
-# story: e09s01
-# story: e45s27
-# story: e21s04
+<!-- story: e09s01 -->
+<!-- story: e45s27 -->
+<!-- story: e21s04 -->
 
 # Compose Workflow
 > **HARD GATE** — **HARD GATE** — Workflows are orchestration, not automation. Do NOT create workflows for tasks that should be single skills. Workflow complexity must be justified.

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

@@ -4,7 +4,7 @@ model: sonnet
 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)."
 ---
 
-# story: e45s30
+<!-- story: e45s30 -->
 
 # Delegate Task
 > **HARD GATE** — **HARD GATE** — Delegated work must have clear success criteria and verification commands. The delegate must be able to verify completion independently.