plumbbob 0.6.4 → 0.6.6

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "plumbbob",
   "displayName": "PlumbBob",
-  "version": "0.6.4",
+  "version": "0.6.6",
   "description": "Attention-first build process — driver skills + a CLI that keep you the decider; guidance, not enforcement.",
   "author": { "name": "Rob McLarty", "email": "hello@robmclarty.com", "url": "https://robmclarty.com" },
   "homepage": "https://github.com/robmclarty/plumbbob#readme",

package/dist/lib/buildlog.js

@@ -27,7 +27,7 @@ export function appendToSection(content, heading, line) {
 }
 // The Log line `checkpoint` writes for a landed step: dated, names the step (its
 // title when intent.md still carries it), and carries the short SHA. One line of the
-// build's history — `/plumbbob:pb-finish` reads these instead of re-narrating the build.
+// build's history — `/pb-finish` reads these instead of re-narrating the build.
 export function checkpointLogLine(date, step, sha, title) {
     const head = `- ${date} — step ${step} checkpointed · ${sha.slice(0, 9)}`;
     return title !== null && title.length > 0 ? `${head} — ${title}` : head;

package/dist/lib/intent.js

@@ -51,12 +51,13 @@ export function parseStepSeam(content, step) {
     // The seam declaration is the seam line plus any wrapped continuation lines.
     // Truncate each at an HTML-comment opener so a trailing `<!-- ... -->` note
     // (which may carry its own backticks) is never read as a seam token; a
-    // continuation ends at the first line whose pre-comment text has no backtick.
+    // continuation ends at the first line whose pre-comment text has no backtick
+    // or that opens a new sub-bullet (a `- model:` note may carry backticks too, D62).
     const seamStart = seamLines[0] ?? 0;
     const decl = [];
     for (let i = seamStart; i < itemLines.length; i++) {
         const beforeComment = (itemLines[i] ?? '').split('<!--')[0] ?? '';
-        if (i > seamStart && !beforeComment.includes('`')) {
+        if (i > seamStart && (!beforeComment.includes('`') || /^\s*-\s/.test(beforeComment))) {
             break;
         }
         decl.push(beforeComment);

package/dist/lib/orient.js

@@ -49,7 +49,9 @@ export function parseSteps(intent) {
         const block = lines.slice(s.idx, blockEnd).join('\n');
         const dw = /\*\*done when:\*\*\s*(.+)/i.exec(block);
         const doneWhen = dw ? (dw[1] ?? '').trim() : null;
-        return { n: s.n, done: s.done, title: s.title, planned: /done when/i.test(block), doneWhen };
+        const md = /^\s*-\s*model:\s*(.+)$/im.exec(block);
+        const model = md ? (md[1] ?? '').trim() : null;
+        return { n: s.n, done: s.done, title: s.title, planned: /done when/i.test(block), doneWhen, model };
     });
 }
 // Flip step N's `[ ]` checkbox to `[x]` within the `## Steps` section — mechanical
@@ -77,7 +79,7 @@ export function parseOpenQuestions(intent) {
         .length;
 }
 // Open parked items: `- [ ]` lines under `## Park list` (the `park` verb's format).
-// A harvested item is flipped to `- [x]` by `/plumbbob:pb-harvest` and no longer counts; the
+// A harvested item is flipped to `- [x]` by `/pb-harvest` and no longer counts; the
 // `(none yet)` placeholder and the blockquote instructions never match.
 export function parseParked(buildLog) {
     return sectionLines(buildLog, '## Park list').filter((l) => /^-\s+\[ \]\s+\S/.test(l.trim())).length;
@@ -101,22 +103,22 @@ function nextMove(spiking, steps, inFlight, parked) {
         return 'close the spike — `plumbbob spike done`';
     }
     if (inFlight !== null) {
-        return `finish step ${inFlight} — \`/plumbbob:pb-verify\` (or keep editing, then \`/plumbbob:pb-verify\`)`;
+        return `finish step ${inFlight} — \`/pb-verify\` (or keep editing, then \`/pb-verify\`)`;
     }
     // At the boundary (DESIGN): the move follows from the steps.
     const nextUndone = steps.find((s) => !s.done);
     if (nextUndone === undefined) {
         if (steps.length === 0) {
-            return 'plan the first step — `/plumbbob:pb-step`';
+            return 'plan the first step — `/pb-step`';
         }
         // Batch-default: the steps were planned up front, so finishing them usually
-        // means "finish up" — but `/plumbbob:pb-step` can still add an increment if reality grew.
-        const harvest = parked > 0 ? `harvest ${parked} parked idea${parked === 1 ? '' : 's'} — \`/plumbbob:pb-harvest\`; then ` : '';
-        return `${harvest}finish up — \`/plumbbob:pb-finish\` (or \`/plumbbob:pb-step\` to add another increment)`;
+        // means "finish up" — but `/pb-step` can still add an increment if reality grew.
+        const harvest = parked > 0 ? `harvest ${parked} parked idea${parked === 1 ? '' : 's'} — \`/pb-harvest\`; then ` : '';
+        return `${harvest}finish up — \`/pb-finish\` (or \`/pb-step\` to add another increment)`;
     }
     return nextUndone.planned
-        ? `build step ${nextUndone.n} — \`/plumbbob:pb-build\` (or \`/plumbbob:pb-step\` to revise it first)`
-        : `plan step ${nextUndone.n} — \`/plumbbob:pb-step\``;
+        ? `build step ${nextUndone.n} — \`/pb-build\` (or \`/pb-step\` to revise it first)`
+        : `plan step ${nextUndone.n} — \`/pb-step\``;
 }
 export function orient(input) {
     const steps = parseSteps(input.intent);
@@ -134,6 +136,7 @@ export function orient(input) {
         next: nextMove(input.spiking, steps, input.inFlight, parked),
         nextDoneWhen: nextUndone?.doneWhen ?? null,
         nextSeam: seamParse !== null && seamParse.ok ? seamParse.seam : [],
+        nextModel: nextUndone?.model ?? null,
     };
 }
 export function formatOrientation(o) {
@@ -146,7 +149,7 @@ export function formatOrientation(o) {
         if (s !== nextUndone) {
             return head;
         }
-        // Surface the next step's detail so the human can review it (and `/plumbbob:pb-step`-
+        // Surface the next step's detail so the human can review it (and `/pb-step`-
         // revise) before building. Only what's present — a rough step shows neither.
         const detail = [];
         if (o.nextDoneWhen !== null) {
@@ -155,6 +158,9 @@ export function formatOrientation(o) {
         if (o.nextSeam.length > 0) {
             detail.push(`        seam: ${o.nextSeam.join(', ')}`);
         }
+        if (o.nextModel !== null) {
+            detail.push(`        model: ${o.nextModel}`);
+        }
         return detail.length > 0 ? [head, ...detail].join('\n') : head;
     });
     const stepsBlock = o.steps.length === 0 ? '  (no steps planned yet)' : `  steps  ${doneCount}/${o.steps.length} done\n${stepLines.join('\n')}`;

package/dist/verbs/check.js

@@ -1,5 +1,5 @@
 // `plumbbob check` — run the heavy gate (D16/D24/D32) and report, with NO state
-// change. The read-only half of the verify tick: `/plumbbob:pb-verify` runs this before the
+// change. The read-only half of the verify tick: `/pb-verify` runs this before the
 // pause so the human approves on a known-green check. Exits with the check's own
 // code (0 = green, 1 = red, 2 = the gate itself broke).
 //

package/dist/verbs/checkpoint.js

@@ -5,7 +5,7 @@
 // is already clean — the human's commit skill may have committed first), records the
 // SHA, flips the intent checkbox to `[x]`, and clears any STEP/SEAM (which returns
 // the dashboard to the DESIGN boundary). The diff's author is irrelevant:
-// `/plumbbob:pb-build`, your hands, a vibe session, or another harness all checkpoint
+// `/pb-build`, your hands, a vibe session, or another harness all checkpoint
 // the same way.
 import { appendFileSync, readFileSync, rmSync, writeFileSync } from 'node:fs';
 import { commit, findRepoRoot, headSha, isDirty, stageAll, stagePath, stagedPaths, stagedStat } from "../lib/git.js";
@@ -81,9 +81,10 @@ function planSubject(root) {
     return title ? `plumbbob: plan — ${title}` : 'plumbbob: plan';
 }
 // Step resolution (D3): explicit arg > in-flight STEP file > first undone step in
-// intent.md. Returns null when none can be determined.
+// intent.md. Returns null when none can be determined. A `-m` value is a message,
+// never a step — `checkpoint -m "2"` must not read as step 2.
 function resolveStep(root, args) {
-    const explicit = args.find((a) => /^\d+$/.test(a));
+    const explicit = args.filter((_, i) => args[i - 1] !== '-m').find((a) => /^\d+$/.test(a));
     if (explicit !== undefined) {
         return Number(explicit);
     }
@@ -108,7 +109,7 @@ function warnScopeDrift(root, step) {
     const outside = scopeDrift(stagedPaths(root), seam);
     if (outside.length > 0) {
         process.stderr.write(`plumbbob: heads-up — staged paths outside step ${step}'s seam: ${outside.join(', ')}. ` +
-            `The checkpoint captures them; if that's real scope drift, the plan may need a \`/plumbbob:pb-step\` revision.\n`);
+            `The checkpoint captures them; if that's real scope drift, the plan may need a \`/pb-step\` revision.\n`);
     }
 }
 // The seam tokens for the in-flight step: the normalized SEAM file `build` wrote
@@ -135,7 +136,10 @@ function flipIntent(root, step) {
         writeFileSync(intentPath(root), markStepDone(readFileSync(intentPath(root), 'utf8'), step));
     }
     catch {
-        // best-effort bookkeeping; the checkpoint SHA is the source of truth.
+        // Best-effort bookkeeping — the checkpoint SHA is the source of truth — but the
+        // dashboard reads intent.md, so a swallowed failure here makes orientation lie.
+        process.stderr.write(`plumbbob: heads-up — could not flip step ${step} to [x] in intent.md; ` +
+            `the checkpoint is recorded, but the dashboard will still show step ${step} as next. Flip it by hand.\n`);
     }
 }
 // Append a dated line to the build-log's `## Log` so the build's history accrues at
@@ -179,9 +183,10 @@ function messageArg(args) {
 // so the skill can compose proportional prose the CLI never could. Returns null
 // when the flag is absent or stdin is empty — either way the deterministic
 // fallback body takes over. Reading fd 0 blocks until EOF, which the heredoc
-// supplies; a read error (no stdin attached) degrades to the fallback.
+// supplies; a read error (no stdin attached) degrades to the fallback, and an
+// interactive TTY — which would never send EOF — skips the read instead of hanging.
 function bodyArg(args) {
-    if (!args.includes('--body')) {
+    if (!args.includes('--body') || process.stdin.isTTY === true) {
         return null;
     }
     try {

package/dist/verbs/doctor.js

@@ -5,7 +5,7 @@
 //    Code loads it in place as a plugin (skills `/plumbbob:*`, the post-edit hook from
 //    hooks.json). doctor verifies the link resolves to a package carrying the manifest,
 //    the skills, and the hook — and names the fix for anything missing. The failure
-//    class it exists for is SILENT (a `/plumbbob:pb-status` that opens an empty dashboard
+//    class it exists for is SILENT (a `/pb-status` that opens an empty dashboard
 //    because the plugin never linked).
 //
 // 2. The repo sidecar layout. A repo scaffolded by a pre-restructure plumbbob carries a
@@ -419,7 +419,7 @@ export async function doctor(cwd, args = []) {
     out.push(failed === 0
         ? 'plumbbob: all checks passed. If a skill still misbehaves, restart Claude Code (or /reload-plugins).'
         : `plumbbob: ${failed} problem(s) — apply the → fixes, then restart Claude Code.`);
-    out.push('plumbbob: skills shell a bare `plumbbob`. The marketplace plugin puts it on PATH only inside a Claude Code session (via bin/) — there is no terminal `plumbbob`; for one (or the skills-dir install) run `npm i -g plumbbob`. In-session you can also run this as `/plumbbob:pb-doctor`. Sessions are per-project via `plumbbob start`.');
+    out.push('plumbbob: skills shell a bare `plumbbob`. The marketplace plugin puts it on PATH only inside a Claude Code session (via bin/) — there is no terminal `plumbbob`; for one (or the skills-dir install) run `npm i -g plumbbob`. In-session you can also run this as `/pb-doctor`. Sessions are per-project via `plumbbob start`.');
     process.stdout.write(`${out.join('\n')}\n`);
     return failed === 0 ? 0 : 1;
 }

package/dist/verbs/finish.js

@@ -23,7 +23,7 @@ export function finish(cwd, args = []) {
     }
     else {
         process.stderr.write('plumbbob: note — no report.md found; finishing without one ' +
-            '(/plumbbob:pb-finish normally writes the report first). No gate (D9).\n');
+            '(/pb-finish normally writes the report first). No gate (D9).\n');
     }
     // The final commit (D34): stage the report just written plus the build folder's
     // tail (the last step's checkpoint line lands one commit late, D37) and commit it
@@ -49,7 +49,7 @@ export function finish(cwd, args = []) {
     rmSync(join(sidecarDir(root), 'STATE'), { force: true });
     const where = slug === null ? '.plumbbob/' : `.plumbbob/builds/${slug}/`;
     process.stdout.write(`plumbbob: finished — ${sha.slice(0, 9)}. ${where} rides your branch into the PR. ` +
-        'Run `/plumbbob:pb-plan` (or `plumbbob start "<title>"`) to frame the next goal.\n');
+        'Run `/pb-plan` (or `plumbbob start "<title>"`) to frame the next goal.\n');
     return 0;
 }
 // The CLI-owned final-commit subject (D34): `plumbbob: finish — <title>`, mirroring

package/dist/verbs/park.js

@@ -1,5 +1,5 @@
 // `plumbbob park "<text>"` — the dumb capture path: append one raw line under
-// the build-log's Park list. No model turn, no composition (that is /plumbbob:pb-park's job).
+// the build-log's Park list. No model turn, no composition (that is /pb-park's job).
 // Capture is not a transition, so it runs in any context (terminal or in-session).
 import { readFileSync, writeFileSync } from 'node:fs';
 import { findRepoRoot } from "../lib/git.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "plumbbob",
-  "version": "0.6.4",
+  "version": "0.6.6",
   "description": "Attention-first build process: 12 skills + a CLI that keep you the decider — guidance, not enforcement.",
   "keywords": [
     "claude-code",

package/skills/pb-build/SKILL.md

@@ -3,7 +3,6 @@ name: pb-build
 description: The default engine — read the next planned step from intent, implement it (its done-when, seam, Decisions, Constraints), then verify it through to the approval pause. Swappable — build by hand/vibed/another harness and run /pb-verify instead. `--auto` self-approves and chains to done; a step range like `1-3` self-approves through step 3, then pauses.
 argument-hint: "[step-number | step-range] [--auto]"
 disable-model-invocation: true
-model: opus
 allowed-tools: Read, Edit, Write, Bash(plumbbob status:*), Bash(plumbbob build:*), Bash(plumbbob check:*), Bash(plumbbob checkpoint:*), Bash(plumbbob agent:*), Bash(git diff:*)
 ---
 
@@ -12,7 +11,7 @@ allowed-tools: Read, Edit, Write, Bash(plumbbob status:*), Bash(plumbbob build:*
 Current session state (injected when this skill runs): !`plumbbob status 2>/dev/null || echo "plumbbob CLI not on PATH in this session. Marketplace install: confirm the plugin is enabled in /plugin, then /reload-plugins. Skills-dir/global install: npm i -g plumbbob && plumbbob init."`
 
 This is the **bundled executor** — the default engine, not the only one. It is
-**swappable** (D3): you can implement any step by hand, in a vibe session, or with
+**swappable**: you can implement any step by hand, in a vibe session, or with
 another harness and go straight to `/pb-verify` instead — plumbbob does not care how
 the diff appeared. When you do run it, it reads the plan, writes the step, and
 carries straight through to the verify pause.
@@ -21,6 +20,11 @@ Since `/pb-plan` lays down the whole step list up front, the happy path is to fi
 `/pb-build` once per step until done — each run builds the next undone step and stops
 at the pause for your approval. **Re-firing `/pb-build` is itself the clock tick.**
 
+A model note: this skill **inherits the session model** — nothing pins or switches
+it. If the step you're about to build carries a `- model:` recommendation that
+differs from the model you're running as, say so before implementing — the human can
+`/model` and re-fire to honor it, or wave you on. Advisory, never a gate.
+
 ## What this skill does, in order
 
 1. **Pick the step.** Use the number you were invoked with (e.g. `/pb-build 4`) — or,
@@ -34,7 +38,7 @@ at the pause for your approval. **Re-firing `/pb-build` is itself the clock tick
 3. **Read the plan.** Read the step's **done-when**, its **seam**, and the
    **Decisions** and **Constraints** in `intent.md`. Build to *that* — the deciding
    already happened, off the chat.
-   - **Run any bound `before`-agents** *(D43/D59)*. If the build's `harness.json` binds
+   - **Run any bound `before`-agents**. If the build's `harness.json` binds
      agents to this step's `before` slot, run `plumbbob agent run --step <n> --mode
      before` first: each returns a validated envelope on stdout that plumbbob also
      appends to the step's `handoff.json`, and its `summary`/`body` become **context you
@@ -45,17 +49,17 @@ at the pause for your approval. **Re-firing `/pb-build` is itself the clock tick
    edit — capture it and stay on the step. If you genuinely cannot finish without
    touching more than the seam, that is scope drift: surface it to the human rather
    than sprawling.
-   - **If a `build`-slot agent is bound, delegate the diff to it** *(D43)*. Run
+   - **If a `build`-slot agent is bound, delegate the diff to it**. Run
      `plumbbob agent run --step <n> --mode build` and let that agent author the step's
      code instead of writing it yourself; its envelope reports what it did. You still
-     own the verify tick below — the diff is reviewed the same way whoever wrote it (D3).
-   - **A manifest's `when` prose is your cue to fire an agent mid-build** *(D43/D55)*.
+     own the verify tick below — the diff is reviewed the same way whoever wrote it.
+   - **A manifest's `when` prose is your cue to fire an agent mid-build**.
      The three slots are the only *declarative* lifecycle points; there is no config for
      "a salient moment in the middle." That is judgment, and you are the frontier model
      in the room: when the work reaches the situation a bound agent's `when` (or a step
      `note`) describes, fire `plumbbob agent run <name> --step <n>` yourself. Prose is
      the orchestration language; you are the workflow engine.
-   - **Route a non-`done` envelope by its status** *(D52)*. An agent that returns
+   - **Route a non-`done` envelope by its status**. An agent that returns
      `blocked` couldn't finish (missing input, failed precondition): surface its `notes`,
      let the human unblock, and re-run it — don't work around it. One that returns
      `drift` finished but found the plan no longer matches reality: **stop and send the
@@ -68,9 +72,9 @@ at the pause for your approval. **Re-firing `/pb-build` is itself the clock tick
    still runs everything) → run any bound `after`-agents (`plumbbob agent run --step
    <n> --mode after`) and fold their envelopes into the self-review as **advisory
    input** — they inform, they never gate (checkride gates, the human is the clock; an
-   `after`-agent that could fail a step is the lock in autonomy's costume, D45) →
+   `after`-agent that could fail a step is the lock in autonomy's costume) →
    self-review the diff against the done-when, the Decisions, and the Constraints (a
-   single structured read, D16) → validate → **PAUSE
+   single structured read) → validate → **PAUSE
    for the human's approval** → only on approval, checkpoint with
    `plumbbob checkpoint <n> --body <<'BODY' … BODY` — a commit body **proportional to the
    step** (a line for a trivial change, a short paragraph for a meatier one; no TIL scan,
@@ -85,8 +89,8 @@ at the pause for your approval. **Re-firing `/pb-build` is itself the clock tick
 progress instead of approving each step. It does the same work, but **the agent reviews
 and approves in the human's place**, and it **chains**:
 
-- Build the next step, running its slots in the same order as the default path
-  (D56): bound `before`-agents → implement (or the bound `build`-agent) → bound
+- Build the next step, running its slots in the same order as the default
+  path: bound `before`-agents → implement (or the bound `build`-agent) → bound
   `after`-agents → `check` → self-review → **if the check is green AND the
   self-review finds no done-when / Decision / Constraint mismatch, checkpoint** and move
   straight on to the next planned step. Repeat. `--auto` adds no new machinery — the
@@ -94,7 +98,7 @@ and approves in the human's place**, and it **chains**:
 - **Stop and hand back to the human** the moment any of these is true: the check is red,
   the self-review finds a mismatch (surface exactly what, and do not checkpoint it), a
   bound agent returns `blocked` or `drift` (unblock-and-re-run, or `/pb-refine` — an
-  agent cannot advance the loop, C6), a new decision is needed, no planned steps
+  agent cannot advance the loop), a new decision is needed, no planned steps
   remain, or the top of a requested range is reached.
 
 `--auto` and a step range are the only paths that checkpoint without a human pause, and
@@ -126,14 +130,14 @@ just the one more entry already in the halt list above.
 ## The hard contracts
 
 - **Swappable, never required.** The loop works without this skill; `/pb-verify`
-  checkpoints a hand-built or vibed diff just the same (D3).
+  checkpoints a hand-built or vibed diff just the same.
 - **Build the decided step, not a new one.** Implement what `intent.md` settled. A
   new idea mid-build is a `/pb-park`, not an edit.
 - **Default ends at the pause.** Implement → verify → wait for approval; never
   checkpoint without it. Only an explicit `--auto` or a step range lets the agent approve
   in your place, and it still halts on a red check or any mismatch — a range also stops
   at its top.
-- **Agents feed the beat; they never advance it** (C6/D45). `before` loads context,
+- **Agents feed the beat; they never advance it**. `before` loads context,
   `build` writes the diff, `after` is advisory — none can checkpoint, flip a step, or
   chain. `blocked` → unblock and re-run; `drift` → `/pb-refine`. You are still the one
   who verifies and (bar `--auto`) the human is still the clock.

package/skills/pb-finish/SKILL.md

@@ -2,7 +2,6 @@
 name: pb-finish
 description: Finish the build — write the report (what shipped, decisions, parked/harvested items, deferred tangents), then make the final commit that closes the session. The build folder rides the branch into the PR — no separate archive. Report by default, no gate.
 disable-model-invocation: true
-model: opus
 allowed-tools: Read, Write, Bash(plumbbob status:*), Bash(plumbbob finish:*)
 ---
 
@@ -11,8 +10,8 @@ allowed-tools: Read, Write, Bash(plumbbob status:*), Bash(plumbbob finish:*)
 Current session state (injected when this skill runs): !`plumbbob status 2>/dev/null || echo "plumbbob CLI not on PATH in this session. Marketplace install: confirm the plugin is enabled in /plugin, then /reload-plugins. Skills-dir/global install: npm i -g plumbbob && plumbbob init."`
 
 `/pb-finish` ends the build: it captures what happened, then makes the final commit
-that closes the session. **Report by default** (D9) — no refuse-without-report gate,
-and no separate docs phase. The build folder is tracked (D26/D29): it merges with the
+that closes the session. **Report by default** — no refuse-without-report gate,
+and no separate docs phase. The build folder is tracked: it merges with the
 branch and shows up in the PR, so there is nothing to archive — the folder *is* the
 record.
 
@@ -30,8 +29,8 @@ record.
    - **Deferred tangents** — the harvested items that become future work.
    This is the "yeah, I did that" artifact. Write it by default; the human may edit it.
 2. **Finish.** Run `plumbbob finish`, which appends the checkpoint SHAs to the
-   report and makes the final commit — subject `plumbbob: finish — <title>` (D34),
-   with an optional proportional body via `--body` (the D34 stdin heredoc) — then
+   report and makes the final commit — subject `plumbbob: finish — <title>`,
+   with an optional proportional body via `--body` (the stdin heredoc) — then
    clears the control state (markers, the `activeBuild` cursor, STATE last). The
    build folder stays in place, committed, and rides the branch into the PR.
 3. **Point at the next goal** — `/pb-plan` to frame the next one.
@@ -43,7 +42,7 @@ record.
 - **The log is the history; the report is the synthesis.** `checkpoint` already recorded
   what shipped, step by step — finish applies the *unique additions* (the why, the deferred
   tangents, the final status), it does not rewrite the timeline.
-- **The folder is the archive, never destroy** (C4/D29). `finish` keeps intent +
+- **The folder is the archive, never destroy**. `finish` keeps intent +
   build-log + report in `builds/<slug>/` and commits them; nothing is copied out and
   nothing is deleted but the untracked control markers.
 - **No version bump, no docs phase.** Updating real docs is a separate, explicit ask;

package/skills/pb-harvest/SKILL.md

@@ -2,7 +2,6 @@
 name: pb-harvest
 description: Triage the park list at a step boundary — propose one class (blocker/tangent/pivot) per parked item, write only after the human confirms each, record under ## Harvest, and fold a confirmed blocker into intent.
 disable-model-invocation: true
-model: opus
 allowed-tools: Read, Edit, Bash(plumbbob status:*)
 ---
 
@@ -10,7 +9,7 @@ allowed-tools: Read, Edit, Bash(plumbbob status:*)
 
 Current session state (injected when this skill runs): !`plumbbob status 2>/dev/null || echo "plumbbob CLI not on PATH in this session. Marketplace install: confirm the plugin is enabled in /plugin, then /reload-plugins. Skills-dir/global install: npm i -g plumbbob && plumbbob init."`
 
-`/pb-harvest` is the complement of `/pb-park` (D7): you parked ideas as seeds during a
+`/pb-harvest` is the complement of `/pb-park`: you parked ideas as seeds during a
 build; now, at a boundary, you harvest them — decide what each one is.
 
 ## When to run it — boundary only

package/skills/pb-park/SKILL.md

@@ -12,7 +12,7 @@ allowed-tools: Bash(plumbbob status:*), Bash(plumbbob park:*)
 Current session state (injected when this skill runs): !`plumbbob status 2>/dev/null || echo "plumbbob CLI not on PATH in this session. Marketplace install: confirm the plugin is enabled in /plugin, then /reload-plugins. Skills-dir/global install: npm i -g plumbbob && plumbbob init."`
 
 `/pb-park` is the **capture** half of the loop; `/pb-harvest` is where parked items
-get triaged later (D7). Capturing the instant an idea arrives — instead of acting on
+get triaged later. Capturing the instant an idea arrives — instead of acting on
 it — is the whole point: it protects the step in flight.
 
 ## Wrong-state refusal

package/skills/pb-plan/SKILL.md

@@ -3,7 +3,6 @@ name: pb-plan
 description: "Frame a fresh goal and author the whole plan — Frame, Decisions, Constraints, and all Steps — before any code. Three input modes: no arg interviews you; a file path absorbs a spec; any other text expands your inline intent."
 argument-hint: "[spec-path | intent]"
 disable-model-invocation: true
-model: opus
 allowed-tools: Read, Edit, Write, Bash(plumbbob status:*), Bash(plumbbob start:*), Bash(plumbbob checkpoint:*), Bash(plumbbob agent list:*)
 ---
 
@@ -17,6 +16,11 @@ of your head and onto `intent.md` *before* any code. By default it authors the
 `/pb-build` until done. (Revising a single increment later is the separate `/pb-step`
 move; do not confuse the two.)
 
+A model note: this skill **inherits the session model** — nothing pins or switches
+it. Planning is where frontier-class judgment pays for itself, so if the session is
+running a small model, suggest `/model opus` (or better) before framing — the
+human's call, never a gate.
+
 ## Three input modes (disambiguated for you — no quotes needed)
 
 Look at the argument the human gave and pick the mode yourself:
@@ -54,13 +58,24 @@ an agent can follow with `/pb-build`. The argument only seeds how you get there.
    ```markdown
    1. [ ] <title> — **done when:** <criterion, ideally a test or check result>
       - seam: `<file>`, `<file>`
+      - model: <optional — smallest that can carry it, with the one-phrase why>
    ```
 
    Every step needs a **done-when** `/pb-verify` can check and a **seam** (the exact
    paths it touches). Later steps may be fuzzier than the first — that's fine; they get
    sharpened just-in-time when you reach them with `/pb-step`. Keep each small enough to
    verify in one review pass.
-5. **Offer harness bindings** *(optional — D42/D43)*. If the build will lean on
+
+   **Recommend a model per step where the signal is clear** *(optional)*: the
+   `- model:` sub-line names the **smallest model that can carry the step**, with the
+   one-phrase why — the human buys capability only where the step needs it. E.g.
+   `model: sonnet — mechanical, fully specified by the done-when` for rote edits;
+   `model: opus — strong-assertion test authoring` where the tests do the thinking;
+   `model: fable — subtle cross-cutting design` for judgment-heavy or creative work.
+   It is advisory metadata for the human — `/pb-status` surfaces it before each build —
+   never a gate, and nothing switches models automatically. Write it plain (no
+   backticks) and omit it when any model would do.
+5. **Offer harness bindings** *(optional)*. If the build will lean on
    user-authored agents, author `harness.json` in the build folder (beside `intent.md`)
    and review it at the **same plan pause**, alongside the steps — bindings are
    plan-adjacent configuration, so they converge with the plan. It binds agents to a
@@ -76,15 +91,15 @@ an agent can follow with `/pb-build`. The argument only seeds how you get there.
    }
    ```
 
-   Keep it **bindings + prose only, never a conditional** (C3): the file says *which*
+   Keep it **bindings + prose only, never a conditional**: the file says *which*
    agent, not *when* — the host model reads each manifest's `when` prose and a step's
    `note` and decides when to fire one mid-build. Skip the file entirely when no step
-   uses an agent — the loop runs identically without it (D54). The plan commit picks it
+   uses an agent — the loop runs identically without it. The plan commit picks it
    up automatically (it lives in the build folder).
 6. **Commit the plan.** Once the human approves the frame and steps, run
    `plumbbob checkpoint --plan` to commit the scaffold on its own — subject
    `plumbbob: plan — <title>`, only `.plumbbob/builds/<slug>/`, a `plan <sha>` line in
-   `checkpoints` (D36). This keeps the first step's diff clean, so history reads
+   `checkpoints`. This keeps the first step's diff clean, so history reads
    baseline → plan → steps. Pass a proportional `--body` (the single-quoted stdin
    heredoc) when the rationale is worth carrying; skip it for a small plan. Do this
    only on the human's approval — the plan is their convergence.

package/skills/pb-refine/SKILL.md

@@ -3,7 +3,6 @@ name: pb-refine
 description: Keep intent.md true — attack the plan for holes (append as Open questions) and refine or repair the Frame, Decisions, Constraints, and Steps to match reality. Usable at any point; you propose, the human approves.
 argument-hint: "[focus]"
 disable-model-invocation: true
-model: opus
 allowed-tools: Read, Edit, Bash(plumbbob status:*)
 ---
 

package/skills/pb-status/SKILL.md

@@ -19,4 +19,8 @@ skill carries **no Edit and no Write tool**: the CLI is the source of truth, so
 ## What it does
 
 1. Surface the injected `status` output — the dashboard and its suggested next move.
-2. If it reads `NO ACTIVE SESSION`, tell the human to `/pb-plan` to frame a goal.
+2. If the next step's detail carries a `model:` line, point it out: it is the
+   plan's recommendation of the smallest model that can carry that step, so the human
+   can switch (e.g. `/model sonnet`) before firing `/pb-build` — or ignore it. Guidance,
+   never a gate.
+3. If it reads `NO ACTIVE SESSION`, tell the human to `/pb-plan` to frame a goal.

package/skills/pb-step/SKILL.md

@@ -3,7 +3,6 @@ name: pb-step
 description: Revise the next increment just-in-time — sharpen the next undone step against what's now true, or (with input) re-cut, split, or add a step. Empty input runs an automatic sharpen. One at a time; the human approves.
 argument-hint: "[what-changed]"
 disable-model-invocation: true
-model: opus
 allowed-tools: Read, Edit, Write, Bash(plumbbob status:*), Bash(plumbbob agent list:*)
 ---
 
@@ -36,17 +35,19 @@ grew — but its everyday job is to sharpen, not to invent.
 2. **Propose the revision** (or the new/split step): a one-line **title**, a **done-when**
    `/pb-verify` can validate, and a **seam** (exact paths, or a `dir/` grant). Keep it
    small enough to verify in one review pass. Show the before/after so the human can see
-   what you changed and why.
+   what you changed and why. Re-check the optional `- model:` recommendation too:
+   a step that sharpened into rote work can drop to a smaller model; one that grew subtle
+   earns a frontier one. Advisory, plain text (no backticks), never a gate.
 3. **Get the human's OK**, then write it into `## Steps` in the standard format —
    `N. [ ] <title> — **done when:** <criterion>` with a `- seam:` sub-line. Revise the
    existing step in place; only append when you are genuinely adding an increment.
-4. **Revise the step's harness bindings if they drifted too** *(optional — D42)*. If the
+4. **Revise the step's harness bindings if they drifted too** *(optional)*. If the
    build carries a `harness.json` (beside `intent.md`) and the reality that moved the
    step also changed which agents it wants, sharpen that step's slot bindings
    (`before`/`build`/`after`) and `note` at the same time — this is the just-in-time
    counterpart to `/pb-plan`'s plan-time binding. `plumbbob agent list` shows what's
    resolvable. Same rule as the plan move: bindings + prose only, never a conditional
-   (C3). Leave it untouched when the step's agents are still right, or when the build
+  . Leave it untouched when the step's agents are still right, or when the build
    uses none.
 
 ## The hard contracts

package/skills/pb-verify/SKILL.md

@@ -2,7 +2,6 @@
 name: pb-verify
 description: "The verify tick — run the check, self-review the diff against intent, validate the step's done-when, pause for your approval, then checkpoint. Executor-agnostic: it reads the diff, not who wrote it."
 disable-model-invocation: true
-model: opus
 allowed-tools: Read, Bash(plumbbob status:*), Bash(plumbbob check:*), Bash(plumbbob checkpoint:*), Bash(plumbbob agent:*), Bash(git diff:*), Bash(git status:*)
 ---
 
@@ -12,29 +11,29 @@ Current session state (injected when this skill runs): !`plumbbob status 2>/dev/
 
 This is the **tick** — the one beat where the human is the clock. Whatever produced
 the current diff — `/pb-build`, your own hands, a vibe session, another harness —
-this skill verifies it the same way: **it reads the diff, not the author** (D3).
+this skill verifies it the same way: **it reads the diff, not the author**.
 
 ## What this skill does, in order
 
 1. **Check.** Run `plumbbob check` (the heavy gate — checkride unless the repo
-   configures a `check` override, D32). If it comes back **red**, stop here: the gate
+   configures a `check` override). If it comes back **red**, stop here: the gate
    names the failing slots and where each tool's raw output landed — read
    `.check/summary.json`, then the failing slot's own file (`.check/<slot>.json` or
    `.check/<slot>.stdout.txt`) for the actual diagnostics instead of scraping
    scrollback. Report what failed and do **not** pause for approval — there is
    nothing to approve yet. The human fixes it and re-invokes. (Exit 2 means the gate
    itself broke — a harness problem to surface, not a code failure.)
-2. **Run any bound `after`-agents** *(optional — D45)*. If the build's `harness.json`
+2. **Run any bound `after`-agents** *(optional)*. If the build's `harness.json`
    binds agents to this step's `after` slot, run `plumbbob agent run --step <n> --mode
    after`. Their envelopes are **advisory input to the self-review, never a gate** —
    `plumbbob check` already gated in step 1, and an `after`-agent that could fail a step
-   is the lock returning in autonomy's costume (D45). Fold a `done` envelope's
-   `summary`/`body` into the review below; route a non-`done` one by its status (D52): a
+   is the lock returning in autonomy's costume. Fold a `done` envelope's
+   `summary`/`body` into the review below; route a non-`done` one by its status: a
    `blocked` agent couldn't finish — surface its `notes`, let the human unblock, re-run;
    a `drift` agent found the plan no longer matches reality — stop and send the human to
    `/pb-refine` to repair the plan before checkpointing. No binding, or no harness, is a
    clean no-op.
-3. **Self-review** *(a single structured read, D16)*. Read `git diff` and
+3. **Self-review** *(a single structured read)*. Read `git diff` and
    `.plumbbob/intent.md`, then in one pass check the diff against:
    - the current step's **done-when** criterion — is it actually met?
    - the **Decisions** — does anything contradict a settled call?
@@ -68,12 +67,12 @@ this skill verifies it the same way: **it reads the diff, not the author** (D3).
 
 - **Never skip the pause.** Check → self-review → validate, then wait. Approval is
   the only thing that triggers the checkpoint.
-- **Read the diff, not the author** (D3). Verify identically whether the code was
+- **Read the diff, not the author**. Verify identically whether the code was
   built by `/pb-build`, by hand, vibed, or by another harness.
 - **Red means stop, not pause.** A failing check is not an approval decision; report
   it and end your turn.
 - **You review; you do not build.** If the self-review finds a problem, surface it
   and stop — fixing is a new build beat, not part of verify.
-- **`after`-agents advise; they never gate** (D45). Their output feeds the
+- **`after`-agents advise; they never gate**. Their output feeds the
   self-review — checkride gates, the human approves. `blocked` → unblock and re-run;
   `drift` → `/pb-refine` before checkpointing. No code path makes them blocking.

package/templates/intent.md

@@ -47,12 +47,16 @@ holes `/pb-refine` surfaces, and as blockers fold in during BUILD.)*
 *(The build plan. `/pb-plan` authors the **whole list up front** — each step a small,
 verifiable increment with its own **done-when** and **seam** (the paths it will touch,
 which `/pb-build` records in the build folder's `SEAM` for orientation — awareness, not a lock).
+An optional **model** line recommends the smallest model that can carry the step —
+mechanical work runs fine on a small model; subtle or creative work earns a frontier
+one. Advisory for the human, never a gate; write it plain, no backticks (D62).
 Then drive `/pb-build` until done. Later steps may be fuzzier than the first;
 sharpen the next one just-in-time with `/pb-step` (empty input auto-syncs it), and use
 `/pb-refine` to repair the whole plan when a blocker rewrites it.)*
 
 1. [ ] <step> — **done when:** <criterion, ideally a test or check result>
    - seam: `<file>`, `<file>`
+   - model: <smallest that can carry it, e.g. sonnet — mechanical, fully specified>
 2. [ ] <step> — **done when:** <criterion>
    - seam: `<file>`