@iceinvein/agent-skills 0.23.0 → 0.23.2

package/README.md

@@ -22,6 +22,22 @@ bunx @iceinvein/agent-skills install                         # no args: opens pi
 
 Auto-detects Claude Code, Cursor, Codex, or Gemini CLI. Use `--tool claude` to target one, `-g` to install globally.
 
+### Claude Code plugin
+
+Each skill is also a plugin in the `iceinvein-skills` marketplace:
+
+```
+/plugin marketplace add iceinvein/agent-skills
+/plugin install <skill>@iceinvein-skills
+```
+
+- Plugin skills are namespaced: invoke them as `/<skill>:<skill>` (e.g. `/sluice:sluice`).
+- Third-party marketplaces do not auto-update by default. Update from `/plugin`.
+- Activation modes do not apply: sluice's hooks always run while the plugin is enabled, and terse is never auto-activated.
+- Do not install sluice through both routes, or its hooks run twice. Its statusline segment is bunx-only.
+- magpie, migrate and scope-estimate need Bun on PATH.
+- improve-my-codebase's plugin carries every audit, so under the plugin route its audits do not need installing separately.
+
 ## Skills
 
 ### Migration

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iceinvein/agent-skills",
-  "version": "0.23.0",
+  "version": "0.23.2",
   "description": "Install agent skills into AI coding tools",
   "author": "iceinvein",
   "license": "MIT",

package/skills/bug-hunter/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: bug-hunter
 description: Use when asked to hunt for bugs or edge cases in a change or area, to say what QA will find before QA does, or to prove a change correct. Runs QA-style scenarios as failing reproductions in the repo's own test runner and reports only bugs it can prove, plus the questions intent leaves open.
+argument-hint: "[<commit>|<base>..<head>|<path>...]"
 ---
 
 # Bug hunter
@@ -12,7 +13,8 @@ a failing reproduction, checked against what the change was meant to do.
 ## Method
 
 1. **Name the target** in one line: a diff (a commit, a range, the working
-   changes) or a set of paths. Every later step is scoped to it.
+   changes) or a set of paths, taken from the arguments when given and the
+   working changes otherwise. Every later step is scoped to it.
 2. **Collect intent** into `intent.md`: numbered claims (`I1`, `I2`, ...),
    each one checkable statement with its source. Sources are the request or
    ticket, commit messages, specs and designs, docs, `CLAUDE.md`/`AGENTS.md`,

package/skills/bug-hunter/skill.json

@@ -1,6 +1,6 @@
 {
   "name": "bug-hunter",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "description": "Hunts logic and correctness bugs in a change or area and proves each one with a failing reproduction checked against stated intent. One agent collects intent from the request, specs, docs and unchanged code, runs QA-style scenarios from a catalog as repros in the repo's own test runner inside a scratch copy, and re-runs each failure clean before reporting it. Counts a contradicted claim, or a result wrong under every reading, as a bug; keeps ambiguities for questions with more than one acceptable answer; reports latent defects without filing them. No repro, no finding. Writes report.md and findings.json (bugs, ambiguities, covered) to .bug-hunter/<date>-<slug>/ and never modifies the caller's tree. Language-agnostic; ships no per-language scripts.",
   "author": "iceinvein",
   "type": "prompt",

package/skills/improve-my-codebase/skill.json

@@ -1,9 +1,12 @@
 {
   "name": "improve-my-codebase",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Orchestrator skill that runs every applicable audit skill in parallel and produces a prioritized, convergence-ranked improvement report",
   "author": "iceinvein",
   "type": "prompt",
+  "plugin": {
+    "bundleSiblings": true
+  },
   "tools": [
     "claude",
     "cursor",

package/skills/index.json

@@ -13,7 +13,7 @@
     "name": "bug-hunter",
     "description": "Hunts logic and correctness bugs in a change or area and proves each one with a failing reproduction checked against stated intent. One agent collects intent from the request, specs, docs and unchanged code, runs QA-style scenarios from a catalog as repros in the repo's own test runner inside a scratch copy, and re-runs each failure clean before reporting it. Counts a contradicted claim, or a result wrong under every reading, as a bug; keeps ambiguities for questions with more than one acceptable answer; reports latent defects without filing them. No repro, no finding. Writes report.md and findings.json (bugs, ambiguities, covered) to .bug-hunter/<date>-<slug>/ and never modifies the caller's tree. Language-agnostic; ships no per-language scripts.",
     "type": "prompt",
-    "version": "0.4.1"
+    "version": "0.4.2"
   },
   {
     "name": "codebase-architecture",
@@ -211,7 +211,7 @@
     "name": "improve-my-codebase",
     "description": "Orchestrator skill that runs every applicable audit skill in parallel and produces a prioritized, convergence-ranked improvement report",
     "type": "prompt",
-    "version": "1.1.0"
+    "version": "1.1.1"
   },
   {
     "name": "integration-pattern-auditor",
@@ -225,15 +225,15 @@
   },
   {
     "name": "magpie",
-    "description": "Interactive PR review pipeline. Runs five parallel specialist subagents (security, bugs, performance, code-smells, architecture) plus a once-per-PR checks pass that finds tests and controls able to pass without proving their purpose, drops findings whose quoted evidence is not in the code, dedupes, runs critic subagents that re-check each finding against the worktree and set its risk label, peer-reviews via codex exec (falling back to a Claude second opinion when codex is unavailable), and serves an interactive HTML report for selecting or dismissing findings to post via gh, recording the outcome per finding as labels. Bundles a Bun CLI installed onto PATH via the skill's postinstall step. Use when the user asks to review a GitHub pull request, or to self-review the current branch diff before a PR exists, typically requested by an implementing or orchestrating agent, with findings handed back in the terminal. Splits oversized diffs into budgeted shards and rebuilds the diff from the local clone when gh pr diff refuses it.",
+    "description": "Interactive PR review pipeline. Runs five parallel specialist subagents (security, bugs, performance, code-smells, architecture) plus a once-per-PR checks pass that finds tests and controls able to pass without proving their purpose, drops findings whose quoted evidence is not in the code, dedupes, runs critic subagents that re-check each finding against the worktree and set its risk label, peer-reviews via codex exec (falling back to a Claude second opinion when codex is unavailable), and serves an interactive HTML report for selecting or dismissing findings to post via gh, recording the outcome per finding as labels. Bundles a Bun CLI put on PATH by the skill's postinstall step under a bunx install, or by the plugin's bin/ under a Claude Code plugin install. Use when the user asks to review a GitHub pull request. Local mode (setup --local) runs the same pipeline on the current branch's diff from its merge base, uncommitted and untracked work included, against the caller's live tree, with no server or posting, and hands the ranked findings back in the terminal for an implementing or orchestrating agent to address. Splits oversized diffs into budgeted shards and rebuilds the diff from the local clone when gh pr diff refuses it.",
     "type": "prompt",
-    "version": "0.14.0"
+    "version": "0.14.5"
   },
   {
     "name": "migrate",
     "description": "Source-agnostic legacy migration mapping. Walks a legacy codebase through probe, enumerate, seam, extract, parity, queue, adjudicate and handoff, building an auditable requirements ledger with mandatory citations and a `migrate check` gate in place of self-reported completeness. Use when the user asks to migrate, re-specify, replatform, or map a legacy system onto a new stack, to hand mapped requirements to a delivery team, or to resume, check, report, or forecast a mapping run already under way.",
     "type": "prompt",
-    "version": "0.4.1"
+    "version": "0.4.3"
   },
   {
     "name": "module-secret-auditor",
@@ -269,7 +269,7 @@
     "name": "scope-estimate",
     "description": "Scopes and estimates a rebuild or respec of an existing system for a proposal: read-only discovery agents write cited inventories, a capability register gives every capability a status and a proposed disposition, area agents turn it into sized functional requirements, and a bundled Bun scheduler groups them into slices and contracts-first work packages and schedules them across engineers x worktrees at fast, planning and floor rates. The scheduler refuses a plan that misses or double-counts a requirement or has a dependency cycle, so every figure in the docs comes from one reproducible run. Also covers current and target architecture pages, proposal review, and a two-week calibration before committing to a date. Lighter than migrate: no store and no phase gates.",
     "type": "prompt",
-    "version": "0.1.0"
+    "version": "0.1.3"
   },
   {
     "name": "seam-finder",
@@ -293,9 +293,9 @@
   },
   {
     "name": "sluice",
-    "description": "Routes work by change shape into four channels (bypass, fast, main, deep) and applies only the rules each channel needs, so a one-line fix does not pay the cost of a multi-subsystem build. Carries nine rules as one-liners in the router and the full treatment in references read only on friction. Checks the finished plan with plan.sh validate rather than trusting it to memory, seeds the run state from it, keeps a deep run's task breakdown in .sluice/run.json so a statusline segment, one status command and a SessionStart hook can answer where the run is (the hook prints a live run at every session start, compaction included), and closes each run with a ledger read out of the session transcript: elapsed, tools, tokens, and what each dispatched agent cost where the transcript recorded it. Claude Code only; stands down where the superpowers pipeline governs the repo.",
+    "description": "Routes work by change shape into four channels (bypass, fast, main, deep) and applies only the rules each channel needs, so a one-line fix does not pay the cost of a multi-subsystem build. Carries nine rules as one-liners in the router and the full treatment in references read only on friction. Checks the finished plan with plan.sh validate rather than trusting it to memory, seeds the run state from it, keeps a deep run's task breakdown in .sluice/run.json so a statusline segment, one status command and a SessionStart hook can answer where the run is (the hook prints a live run at every session start, compaction included), and closes each run with a ledger read out of the session transcript: elapsed, tools, tokens, and what each dispatched agent cost where the transcript recorded it. Two Stop hooks hold a handback: one refuses a tree that moved since its last recorded check, the other refuses a changed existing test not proven to fail on the session's starting code (or recorded with a reason). Claude Code only; stands down where the superpowers pipeline governs the repo.",
     "type": "prompt",
-    "version": "0.25.0"
+    "version": "0.25.2"
   },
   {
     "name": "temporal-coupling-detector",

package/skills/magpie/README.md

@@ -19,7 +19,15 @@ Given a GitHub PR number, dispatches five specialist subagents in parallel (secu
 bunx @iceinvein/agent-skills install magpie -g
 ```
 
-This skill ships in two parts: the prompt (SKILL.md) and a companion Bun CLI (bin + scripts). The agent-skills installer writes both into `~/.claude/skills/magpie/` and then runs the bundled `install.sh` as a postinstall step, which symlinks `bin/magpie` onto your PATH (preferring `/usr/local/bin`, falling back to `~/.local/bin`). Removing the skill with `agent-skills remove magpie -g` runs `uninstall.sh` first to undo the PATH symlink.
+As a Claude Code plugin, after `/plugin marketplace add iceinvein/agent-skills`:
+
+```
+/plugin install magpie@iceinvein-skills
+```
+
+This skill ships in two parts: the prompt (SKILL.md) and a companion Bun CLI (bin + scripts). The agent-skills installer writes both into `~/.claude/skills/magpie/` and then runs the bundled `install.sh` as a postinstall step, which symlinks `bin/magpie` onto your PATH (preferring `/usr/local/bin`, falling back to `~/.local/bin`). Set `MAGPIE_BIN_DIR` to link into that directory instead; it is created if missing, and install.sh fails rather than falling back when it cannot link there. Removing the skill with `agent-skills remove magpie -g` runs `uninstall.sh` first to undo the PATH symlink.
+
+Under a Claude Code plugin install, the plugin's `bin/` puts `magpie` on your PATH, and `bin/magpie` installs its runtime dependencies on first run (Bun required). `install.sh` and `MAGPIE_BIN_DIR` apply only to the bunx install.
 
 If you cloned this repo and want to run from source, you can also invoke `./install.sh` directly: it does the PATH-link step against the local source tree.
 

package/skills/magpie/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: magpie
 description: Use when the user asks to review a GitHub pull request (a PR number, PR URL, or "review this PR"), or to self-review the current branch diff before a PR exists, typically requested by an implementing or orchestrating agent, with findings handed back in the terminal. Interactive PR review pipeline; five parallel specialist subagents, dedupe, critic, codex/Claude peer review, and an interactive HTML report for posting selected findings via gh. Follow the stage walkthrough in this skill; the description is not the procedure.
+argument-hint: "[<pr#>|<pr-url>|local] [--base <ref>] [--intent-file <path>]"
 ---
 
 # Magpie
@@ -15,7 +16,7 @@ Stop reading and follow these steps in order. Do not skip stages. Use the exact
 
 ### 0. Identify the PR
 
-A request with no PR that asks to review the current branch, the working tree, or work in progress is local mode: follow "Local mode" below in place of this step and stages 1 and 2, then run stages 3 to 7 as written, taking `TARGET` from Local mode.
+A request with no PR that asks to review the current branch, the working tree, or work in progress, or arguments starting `local` (any `--base` or `--intent-file` after it go to setup), is local mode: follow "Local mode" below in place of this step and stages 1 and 2, then run stages 3 to 7 as written, taking `TARGET` from Local mode.
 
 Parse the user's request for a PR number, URL, or "this PR" (current branch). If ambiguous, ask one clarifying terminal question. Capture the PR number into `$PR_NUMBER` and the repo path into `$REPO` (default: the current working directory).
 

package/skills/magpie/bin/magpie

@@ -12,4 +12,21 @@ while [ -L "$SCRIPT" ]; do
   fi
 done
 DIR="$(cd -P "$(dirname "$SCRIPT")" && pwd)"
+ROOT="$(dirname "$DIR")"
+
+# A plugin install puts bin/ on PATH without running install.sh, so the
+# first run has to fetch runtime dependencies itself. Progress goes to stderr
+# because callers parse magpie's stdout. The gate is a marker written after
+# success, not node_modules itself, because a failed or killed install leaves
+# node_modules behind and the next run would skip straight to a crash.
+MARKER="$ROOT/node_modules/.magpie-deps-installed"
+if [ -f "$ROOT/package.json" ] && [ ! -f "$MARKER" ]; then
+  echo "Installing magpie runtime dependencies..." >&2
+  (cd "$ROOT" && bun install --production --silent) >&2 || {
+    echo "magpie: bun install failed in $ROOT" >&2
+    exit 1
+  }
+  touch "$MARKER"
+fi
+
 exec bun "$DIR/magpie.ts" "$@"

package/skills/magpie/install.sh

@@ -18,14 +18,18 @@ chmod +x "$BIN_SOURCE" || true
 
 # Magpie has runtime dependencies (shiki, etc.) declared in package.json.
 # node_modules is not shipped via npm, so we populate it here. Use bun if
-# available; fall back to a clear error otherwise.
-if [ -f "$SOURCE_DIR/package.json" ] && [ ! -d "$SOURCE_DIR/node_modules" ]; then
+# available; fall back to a clear error otherwise. The gate and marker match
+# bin/magpie's first-run install, so the wrapper does not install again, and a
+# failed install here leaves no marker and is retried on the next run.
+MARKER="$SOURCE_DIR/node_modules/.magpie-deps-installed"
+if [ -f "$SOURCE_DIR/package.json" ] && [ ! -f "$MARKER" ]; then
   if command -v bun >/dev/null 2>&1; then
     echo "Installing magpie runtime dependencies..."
     (cd "$SOURCE_DIR" && bun install --production --silent) || {
       echo "magpie postinstall: bun install failed in $SOURCE_DIR" >&2
       exit 1
     }
+    touch "$MARKER"
   else
     echo "magpie postinstall: bun not found on PATH; install Bun (https://bun.sh) and rerun this script." >&2
     exit 1
@@ -56,7 +60,21 @@ install_link() {
 echo "Installing magpie CLI on PATH:"
 
 CLI_INSTALL_DIR=""
-if install_link "/usr/local/bin"; then
+# An explicit MAGPIE_BIN_DIR is the only place the caller wants the link, so a
+# failure there is an error rather than a cue to try the default locations.
+if [ -n "${MAGPIE_BIN_DIR:-}" ]; then
+  # The recorded path is read by uninstall.sh from any cwd, so it must be absolute.
+  case "$MAGPIE_BIN_DIR" in
+    /*) ;;
+    *) MAGPIE_BIN_DIR="$PWD/$MAGPIE_BIN_DIR" ;;
+  esac
+  if install_link "$MAGPIE_BIN_DIR"; then
+    CLI_INSTALL_DIR="$MAGPIE_BIN_DIR"
+  else
+    echo "magpie postinstall: could not link magpie into MAGPIE_BIN_DIR ($MAGPIE_BIN_DIR)" >&2
+    exit 1
+  fi
+elif install_link "/usr/local/bin"; then
   CLI_INSTALL_DIR="/usr/local/bin"
 elif install_link "$HOME/.local/bin"; then
   CLI_INSTALL_DIR="$HOME/.local/bin"

package/skills/magpie/skill.json

@@ -1,7 +1,7 @@
 {
   "name": "magpie",
-  "version": "0.14.0",
-  "description": "Interactive PR review pipeline. Runs five parallel specialist subagents (security, bugs, performance, code-smells, architecture) plus a once-per-PR checks pass that finds tests and controls able to pass without proving their purpose, drops findings whose quoted evidence is not in the code, dedupes, runs critic subagents that re-check each finding against the worktree and set its risk label, peer-reviews via codex exec (falling back to a Claude second opinion when codex is unavailable), and serves an interactive HTML report for selecting or dismissing findings to post via gh, recording the outcome per finding as labels. Bundles a Bun CLI installed onto PATH via the skill's postinstall step. Use when the user asks to review a GitHub pull request, or to self-review the current branch diff before a PR exists, typically requested by an implementing or orchestrating agent, with findings handed back in the terminal. Splits oversized diffs into budgeted shards and rebuilds the diff from the local clone when gh pr diff refuses it.",
+  "version": "0.14.5",
+  "description": "Interactive PR review pipeline. Runs five parallel specialist subagents (security, bugs, performance, code-smells, architecture) plus a once-per-PR checks pass that finds tests and controls able to pass without proving their purpose, drops findings whose quoted evidence is not in the code, dedupes, runs critic subagents that re-check each finding against the worktree and set its risk label, peer-reviews via codex exec (falling back to a Claude second opinion when codex is unavailable), and serves an interactive HTML report for selecting or dismissing findings to post via gh, recording the outcome per finding as labels. Bundles a Bun CLI put on PATH by the skill's postinstall step under a bunx install, or by the plugin's bin/ under a Claude Code plugin install. Use when the user asks to review a GitHub pull request. Local mode (setup --local) runs the same pipeline on the current branch's diff from its merge base, uncommitted and untracked work included, against the caller's live tree, with no server or posting, and hands the ranked findings back in the terminal for an implementing or orchestrating agent to address. Splits oversized diffs into budgeted shards and rebuilds the diff from the local clone when gh pr diff refuses it.",
   "author": "iceinvein",
   "type": "prompt",
   "tools": [

package/skills/migrate/README.md

@@ -185,6 +185,12 @@ writing.
 bunx @iceinvein/agent-skills install migrate -g
 ```
 
+As a Claude Code plugin, after `/plugin marketplace add iceinvein/agent-skills`:
+
+```
+/plugin install migrate@iceinvein-skills
+```
+
 This skill ships in two parts: the prompt (`SKILL.md`) and a companion Bun
 CLI (`bin` + `scripts`). The agent-skills installer writes both into
 `~/.claude/skills/migrate/` and then runs the bundled `install.sh` as a

package/skills/migrate/SKILL.md

@@ -7,7 +7,8 @@ description: Source-agnostic legacy migration mapping. Walks a legacy codebase t
 
 ## Prerequisites
 
-- `migrate` on `PATH`, put there by this skill's `install.sh`.
+- `migrate` on `PATH`, put there by this skill's `install.sh` under a bunx
+  install, or by the plugin's `bin/` under a Claude Code plugin install.
 - A read-only checkout of the legacy source. `migrate check`'s `citations` and
   `source` gates read it; nothing here writes to it, and every writer in the CLI
   refuses a path that resolves inside it.

package/skills/migrate/skill.json

@@ -1,6 +1,6 @@
 {
   "name": "migrate",
-  "version": "0.4.1",
+  "version": "0.4.3",
   "description": "Source-agnostic legacy migration mapping. Walks a legacy codebase through probe, enumerate, seam, extract, parity, queue, adjudicate and handoff, building an auditable requirements ledger with mandatory citations and a `migrate check` gate in place of self-reported completeness. Use when the user asks to migrate, re-specify, replatform, or map a legacy system onto a new stack, to hand mapped requirements to a delivery team, or to resume, check, report, or forecast a mapping run already under way.",
   "author": "iceinvein",
   "type": "prompt",

package/skills/scope-estimate/README.md

@@ -37,7 +37,7 @@ It updates the requirements, re-runs the scheduler and every page that quotes
 a figure.
 
 **Scheduler on its own:**
-`bun .claude/skills/scope-estimate/scripts/schedule.ts build-plan/requirements build-plan/plan.json --json build-plan/schedule.json`
+`bun <skill-dir>/scripts/schedule.ts build-plan/requirements build-plan/plan.json --json build-plan/schedule.json`
 (`--help` lists the `plan.json` fields).
 
 **Say when presenting:** status is from reading code, not running it; rates
@@ -52,6 +52,12 @@ bunx @iceinvein/agent-skills install scope-estimate        # this project
 bunx @iceinvein/agent-skills install scope-estimate -g     # every project
 ```
 
+As a Claude Code plugin, after `/plugin marketplace add iceinvein/agent-skills`:
+
+```
+/plugin install scope-estimate@iceinvein-skills
+```
+
 Needs [Bun](https://bun.sh) for the scheduler. Claude Code only.
 
 ## Starting a run
@@ -118,15 +124,16 @@ stays a local file until you say otherwise.
 ## The scheduler
 
 ```
-bun .claude/skills/scope-estimate/scripts/schedule.ts <requirements-dir> <plan.json> [--json <out.json>]
+bun <skill-dir>/scripts/schedule.ts <requirements-dir> <plan.json> [--json <out.json>]
 ```
 
-Use `~/.claude/skills/...` for a global install. It prints totals, gated
-totals, per-slice requirements and planning days, the engineers x worktrees
-matrix at planning rates, the headline fast, planning and floor weeks, the
-longest dependency chain, packages sized by assumption and dependencies that
-resolved to nothing. `--json` adds the full report, including the lane order
-for every team combination.
+`<skill-dir>` is the skill's install directory (e.g.
+`.claude/skills/scope-estimate` for a bunx project install). It prints
+totals, gated totals, per-slice requirements and planning days, the
+engineers x worktrees matrix at planning rates, the headline fast, planning
+and floor weeks, the longest dependency chain, packages sized by assumption
+and dependencies that resolved to nothing. `--json` adds the full report,
+including the lane order for every team combination.
 
 It refuses a plan that misses or double-counts a requirement, reuses a
 package id, names an unknown package or undeclared layer, has a dependency

package/skills/scope-estimate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: scope-estimate
-description: Use when asked to scope, size or estimate a rebuild or respec of an existing system for a proposal or engagement, to map what a codebase does into a capability register, to turn capabilities into functional requirements and build slices, or to work out how long an agent-driven team (engineers x worktrees) takes to build it. Lighter than migrate: no store, no CLI gates, presentable docs plus a scheduler script so the numbers add up.
+description: "Use when asked to scope, size or estimate a rebuild or respec of an existing system for a proposal or engagement, to map what a codebase does into a capability register, to turn capabilities into functional requirements and build slices, or to work out how long an agent-driven team (engineers x worktrees) takes to build it. Lighter than migrate: no store, no CLI gates, presentable docs plus a scheduler script so the numbers add up."
 ---
 
 # Scope and estimate
@@ -131,19 +131,20 @@ Complete `build-plan/plan.json` (slices, foundation packages, any split or
 ordered product packages) and run:
 
 ```
-bun .claude/skills/scope-estimate/scripts/schedule.ts build-plan/requirements build-plan/plan.json --json build-plan/schedule.json
+bun <skill-dir>/scripts/schedule.ts build-plan/requirements build-plan/plan.json --json build-plan/schedule.json
 ```
 
-(Use `~/.claude/skills/...` if the skill was installed globally.) It refuses a
-plan that does not account for every requirement exactly once, reuses a
-package id, names an unknown package or undeclared layer, lets scheduled work
-wait on gated work, or has a dependency cycle (naming the requirement behind
-each edge). It prints totals, gated totals, per-slice counts and planning
-days, the engineers x worktrees matrix at planning rates, the headline
-fast/planning/floor range, the critical chain, assumed sizes and unresolved
-dependencies. Fix the plan, not the output. **Every number in the docs comes
-from this output.** Re-run it after any requirement, rate or team change and
-update every page that quotes a figure. Reference: `references/schedule.md`.
+(`<skill-dir>` is this skill's base directory, stated when the skill loads.) It
+refuses a plan that does not account for every requirement exactly once,
+reuses a package id, names an unknown package or undeclared layer, lets
+scheduled work wait on gated work, or has a dependency cycle (naming the
+requirement behind each edge). It prints totals, gated totals, per-slice
+counts and planning days, the engineers x worktrees matrix at planning rates,
+the headline fast/planning/floor range, the critical chain, assumed sizes and
+unresolved dependencies. Fix the plan, not the output. **Every number in the
+docs comes from this output.** Re-run it after any requirement, rate or team
+change and update every page that quotes a figure. Reference:
+`references/schedule.md`.
 
 ### 5. Architecture and proposal checks
 

package/skills/scope-estimate/skill.json

@@ -1,14 +1,25 @@
 {
   "name": "scope-estimate",
-  "version": "0.1.0",
+  "version": "0.1.3",
   "description": "Scopes and estimates a rebuild or respec of an existing system for a proposal: read-only discovery agents write cited inventories, a capability register gives every capability a status and a proposed disposition, area agents turn it into sized functional requirements, and a bundled Bun scheduler groups them into slices and contracts-first work packages and schedules them across engineers x worktrees at fast, planning and floor rates. The scheduler refuses a plan that misses or double-counts a requirement or has a dependency cycle, so every figure in the docs comes from one reproducible run. Also covers current and target architecture pages, proposal review, and a two-week calibration before committing to a date. Lighter than migrate: no store and no phase gates.",
   "author": "iceinvein",
   "type": "prompt",
-  "tools": ["claude"],
-  "files": { "prompt": "SKILL.md" },
+  "tools": [
+    "claude"
+  ],
+  "files": {
+    "prompt": "SKILL.md"
+  },
   "bundle": {
-    "include": ["README.md", "references", "scripts", "templates"],
-    "exclude": ["scripts/__tests__/"]
+    "include": [
+      "README.md",
+      "references",
+      "scripts",
+      "templates"
+    ],
+    "exclude": [
+      "scripts/__tests__/"
+    ]
   },
   "install": {
     "claude": {

package/skills/sluice/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: sluice
 description: Use at the start of any request that changes code. Routes the work into one of four channels (bypass, fast, main, deep) by change shape, and applies only the rules that channel needs. Also use when asked to work faster or with less process.
+argument-hint: "[fast|main|deep] [<what to change>]"
 ---
 
 # Sluice
@@ -119,7 +120,8 @@ Escalate out loud. A `fast` task that turns out to need a new interface becomes
 `main`, and you say so with another `status.sh route` call in that message.
 Finishing quietly in the wrong channel is the failure this prevents; the same
 goes for dropping to a shallower one. Explicit instruction wins: "just do it"
-collapses to `fast`.
+collapses to `fast`, and a channel named when invoking (`/sluice main`) is that
+channel.
 
 ## Deep channel
 

package/skills/sluice/references/deep-channel.md

@@ -431,7 +431,8 @@ reads the run state rather than the plan: it sees what has actually landed.
   task with no `Effort` line goes out on this session's model and effort, and a
   downshift that was neither marked nor ratified is a saving your partner never
   agreed to. A task ratified at `Effort: low` goes out with
-  `subagent_type: sluice-implementer-low`, the agent sluice installs with
+  `subagent_type: sluice-implementer-low` (`sluice:sluice-implementer-low`
+  under a Claude Code plugin install), the agent sluice installs with
   `effort: low` and `model: inherit`: the Agent tool takes a model and no
   effort, so an agent definition is the one place a dispatch's effort can be
   set. Reviewers are the
@@ -533,7 +534,8 @@ something stronger would be promising what is already in use. What a tier buys
 is a dispatch. The one effort rule that holds across all of them is that a
 review never runs below the effort that built the task, so tiers 1 and 2 over
 an `Effort: low` task go out at this session's effort rather than on
-`sluice-implementer-low`.
+`sluice-implementer-low` (`sluice:sluice-implementer-low` under a Claude Code
+plugin install).
 
 **Where the repo carries review tiering of its own, this table governs.** It is
 the more specific of the two: wired into `Flips`, the `Effort` marks and the

package/skills/sluice/scripts/status.sh

@@ -155,8 +155,14 @@ main_tree() { # <dir>
 ORIG_DIR="$DIR"
 if [ "$SUB" != "init" ] && [ ! -f "$DIR/.sluice/run.json" ] \
 	&& [ "$(git -C "$DIR" rev-parse --is-inside-work-tree 2>/dev/null)" = "true" ]; then
+	# The tree's own run lives at its top, not at whatever subdirectory the
+	# session is sitting in. Testing only $DIR sent a session in a worktree's
+	# package straight past that worktree's run to the main tree's.
+	OWN_TREE="$(git -C "$DIR" rev-parse --show-toplevel 2>/dev/null)"
 	MAIN_TREE="$(main_tree "$DIR")"
-	if [ -n "${MAIN_TREE:-}" ] && [ -d "$MAIN_TREE" ]; then
+	if [ -n "${OWN_TREE:-}" ] && [ -f "$OWN_TREE/.sluice/run.json" ]; then
+		DIR="$OWN_TREE"
+	elif [ -n "${MAIN_TREE:-}" ] && [ -d "$MAIN_TREE" ]; then
 		DIR="$MAIN_TREE"
 
 		# Then forward, where the main tree's run has moved on into a worktree.

package/skills/sluice/skill.json

@@ -1,7 +1,7 @@
 {
   "name": "sluice",
-  "version": "0.25.0",
-  "description": "Routes work by change shape into four channels (bypass, fast, main, deep) and applies only the rules each channel needs, so a one-line fix does not pay the cost of a multi-subsystem build. Carries nine rules as one-liners in the router and the full treatment in references read only on friction. Checks the finished plan with plan.sh validate rather than trusting it to memory, seeds the run state from it, keeps a deep run's task breakdown in .sluice/run.json so a statusline segment, one status command and a SessionStart hook can answer where the run is (the hook prints a live run at every session start, compaction included), and closes each run with a ledger read out of the session transcript: elapsed, tools, tokens, and what each dispatched agent cost where the transcript recorded it. Claude Code only; stands down where the superpowers pipeline governs the repo.",
+  "version": "0.25.2",
+  "description": "Routes work by change shape into four channels (bypass, fast, main, deep) and applies only the rules each channel needs, so a one-line fix does not pay the cost of a multi-subsystem build. Carries nine rules as one-liners in the router and the full treatment in references read only on friction. Checks the finished plan with plan.sh validate rather than trusting it to memory, seeds the run state from it, keeps a deep run's task breakdown in .sluice/run.json so a statusline segment, one status command and a SessionStart hook can answer where the run is (the hook prints a live run at every session start, compaction included), and closes each run with a ledger read out of the session transcript: elapsed, tools, tokens, and what each dispatched agent cost where the transcript recorded it. Two Stop hooks hold a handback: one refuses a tree that moved since its last recorded check, the other refuses a changed existing test not proven to fail on the session's starting code (or recorded with a reason). Claude Code only; stands down where the superpowers pipeline governs the repo.",
   "author": "iceinvein",
   "type": "prompt",
   "tools": [