/kbd-pause
Pause the active KBD run. Operator intent always outranks agent continuation.
Progress Signals (MANDATORY)
Before acting, emit:
Starting kbd-pause — <phase-name>
After the checkpoint is durable, emit:
Completed kbd-pause — <phase-name> paused
Procedure
- Resolve the project containing
.kbd-orchestrator/.
- Require a non-empty reason from the arguments or the operator.
- If this project's own runtime CLI is available, run its pause command with
the reason.
- Otherwise create
.kbd-orchestrator/PAUSE first, then atomically update the
waypoint to status: "paused" (via lib/platform/atomic-write.mjs's
atomicWrite), preserving its prior status as previousStatus and
recording pauseReason, pausedAt, and pausedBy. Before writing, call
assertProjectionWritable(root, target) from lib/kbd/runtime-authority.mjs
— it throws when the waypoint is runtime-authoritative, meaning a direct
write here would be out of band.
- Report the last completed work, exact next work, dirty-work summary, and
current plan revision. Do not execute the next command.
Never remove PAUSE, resume work, or reinterpret ordinary prose as a resume.
Selected-method recovery and authority
Before dependent work, run node <pack-root>/scripts/kbd-method-context.mjs --project <project-root> --phase <canonical-phase-id> --write (or read the phase-local method-context.md when Node is unavailable) and act on its status:
RESOLVED_REFERENCES — continue with the recovered method, contract and stage authority; preserve the same references in role inputs, dispatch and handoff read order.
BLOCKED — the contract, its binding, a calibration reference, a supersession or a deviation's cadence/reason is missing or changed, or canonical status is unavailable; resolve it explicitly. Prior commands, memory and tool inventories are not fresh authority.
CONFLICT — a governing rule file the active harness loads grants an exception VLBV forbids (for example a compiler check or an hourly integration gate during generation). Stop before dependent work and show the conflict; continue only after the operator records a KBD-POLICY-ACK decision for that file's current hash. Never rewrite operator-owned policy, and never treat an exception as authority for tests, builds, dry-runs or generated-code verification.
VLBV is the method for every phase (project default verificationMethod: "VLBV"); a deviation exists only as a signed KBD-METHOD decision naming the method, its execution cadence and its reason, and it is disclosed in the closure packet. Define acceptance before generation; generated code executes only at the value-phase boundary (B4) and, after an authorized repair, at B5 — see kbd-process-orchestrator/references/boundaries.md. Tasks, hours, commits, reviewer requests and compiler problems create no boundary. Preserve original evidence, consumed budgets and unresolved effects across resume and supersession; reconcile an uncertain effect before any retry. Full rules: kbd-process-orchestrator/references/method-context.md.
1---2name: kbd-pause3description: Use to gracefully pause the active KBD run, checkpoint its exact position, and prevent every harness from steering execution until an operator resumes it. Operator intent always outranks agent continuation.4license: MIT5metadata:6 source: https://skillmd.com/skills/prometheus-ags/kbd-pause7 version: '1.0.0'8 tags: 'process, orchestration, control, pause'9---1011# /kbd-pause1213Pause the active KBD run. Operator intent always outranks agent continuation.1415## Progress Signals (MANDATORY)1617Before acting, emit:1819```text20Starting kbd-pause — <phase-name>21```2223After the checkpoint is durable, emit:2425```text26Completed kbd-pause — <phase-name> paused27```2829## Procedure30311. Resolve the project containing `.kbd-orchestrator/`.322. Require a non-empty reason from the arguments or the operator.333. If this project's own runtime CLI is available, run its pause command with34 the reason.354. Otherwise create `.kbd-orchestrator/PAUSE` first, then atomically update the36 waypoint to `status: "paused"` (via `lib/platform/atomic-write.mjs`'s37 `atomicWrite`), preserving its prior status as `previousStatus` and38 recording `pauseReason`, `pausedAt`, and `pausedBy`. Before writing, call39 `assertProjectionWritable(root, target)` from `lib/kbd/runtime-authority.mjs`40 — it throws when the waypoint is runtime-authoritative, meaning a direct41 write here would be out of band.425. Report the last completed work, exact next work, dirty-work summary, and43 current plan revision. Do not execute the next command.4445Never remove `PAUSE`, resume work, or reinterpret ordinary prose as a resume.4647## Selected-method recovery and authority4849Before dependent work, run `node <pack-root>/scripts/kbd-method-context.mjs --project <project-root> --phase <canonical-phase-id> --write` (or read the phase-local `method-context.md` when Node is unavailable) and act on its `status`:5051- `RESOLVED_REFERENCES` — continue with the recovered method, contract and stage authority; preserve the same references in role inputs, dispatch and handoff read order.52- `BLOCKED` — the contract, its binding, a calibration reference, a supersession or a deviation's cadence/reason is missing or changed, or canonical status is unavailable; resolve it explicitly. Prior commands, memory and tool inventories are not fresh authority.53- `CONFLICT` — a governing rule file the active harness loads grants an exception VLBV forbids (for example a compiler check or an hourly integration gate during generation). Stop before dependent work and show the conflict; continue only after the operator records a `KBD-POLICY-ACK` decision for that file's current hash. Never rewrite operator-owned policy, and never treat an exception as authority for tests, builds, dry-runs or generated-code verification.5455VLBV is the method for every phase (project default `verificationMethod: "VLBV"`); a deviation exists only as a signed `KBD-METHOD` decision naming the method, its execution cadence and its reason, and it is disclosed in the closure packet. Define acceptance before generation; generated code executes only at the value-phase boundary (B4) and, after an authorized repair, at B5 — see `kbd-process-orchestrator/references/boundaries.md`. Tasks, hours, commits, reviewer requests and compiler problems create no boundary. Preserve original evidence, consumed budgets and unresolved effects across resume and supersession; reconcile an uncertain effect before any retry. Full rules: `kbd-process-orchestrator/references/method-context.md`.56