Note — one referenced asset is absent. This skill names
scripts/refresh-skill-pack.sh, which does not ship in the mini payload; the installed skill-pack refresh procedure is unavailable in this project. See profile and commands for the exact boundary anddocs/maintenance.mdfor update/rollback through the owning harness installer.
Delivery Cadence
The harness owns execution. This skill owns inspectable delivery metadata and procedures, not a second agent loop. Preserve the current goal, KBD phase approvals and canonical task ownership.
Configure
Read project instructions and current work first. Reuse existing choices. Configure iteration duration, build and functional-run commands, human review, publication frequency and explicit optimization bounds in a profile. See profile and commands.
Refreshing an installed skill pack from merged main at a checkpoint is unavailable in this project — no refresh scripts ship in this payload (see the absent-asset note above). Update or roll back an installed payload through its owning harness installer per docs/maintenance.md.
Invoke node <this-skill>/scripts/cadence.mjs <command> --root <state-directory> --input <request.json>. The default state directory is .prometheus/cadence in the current project. Use a stable --command-id when retrying a mutation.
initcreates the run from a profile;configurechanges future policy deliberately.startselects one independently usable increment, with explicit tasks, owners, outcomes and source revisions.- Implement the complete increment, including its UI, strings, persistence and packaging. Keep reviewers dormant. Attach problem/architecture child phases to this delivery using
child enter; the clock continues. Read child recovery before entry or resume. readyrecords completed production scope;candidate freezepins its inputs and operation contract.checkpointbuilds the frozen deliverable, then launches it and exercises its actual function. These are product operations, not test-suite execution. Read pipeline contracts when admitting work-ahead or adopting existing receipts.- Once the current candidate is frozen,
work-ahead admitmay authorize one independent scope in isolated source/output roots while the current build or publication runs. It is not another active iteration or KBD phase. Fix current delivery failures before promotion; only disjoint authorized edits continue during repair. A failed boundary procedure is never simply repeated: the owner authorizes a bounded B5 repair, after which only the affected scenarios rerun. finishrecords the work outcome, dispatches approved hooks and emits the final report. If the last candidate failed, start an evidence-linked corrective iteration, or finalize and explicitly retire that failed iteration withfailure resolvebefore unrelated work. Retirement records a failed outcome, never a successful delivery or phase completion.reviewrecords actual operator approval when a human boundary is due. Never fabricate approval.tickevaluates configured publication opportunities without a daemon. Usepublication attempt/reconcilefor candidate-specific obligations and immutable platform/metadata/site receipts. For an already published release with scope-bound historical debt, usepublication adopt-historical; read historical publication. A dispatch is not publication. Keep one full release in flight and one pending candidate; preserve old debt and separately pending installed acceptance.
New state/reports use schema version 3; profiles and public hook events retain version 1. Use explicit migrate for existing v1/v2 state after stopping old mutators, preserving backups and historical receipts. history links earlier untracked child evidence without counting it as a new delivery.
The active event journal is bounded and older events are kept as checksummed gzip segments under archives/, listed with sequence ranges in event-archives.json. Rotation streams sequence validation and compression without parsing historical full-state events into memory. The latest state still comes from the committed event; state.json is a recovery snapshot. Keep both the manifest and segments when moving or backing up a run. Do not delete or hand-edit them to clear an oversized journal.
A clock tick (B3) stops new scope admission, never certifies unfinished code. Finish the committed increment and report the overrun honestly; the adopted contract's budgets and an operator stop are hard limits that take precedence (budget exhaustion checkpoints the phase BLOCKED). If the harness cannot continue autonomously, leave durable state and a resume instruction; never claim background execution.
VLBV attachment (KBD mode)
Cadence owns delivery rhythm and publication only; acceptance belongs to the KBD
phase and its adopted contract. Boundaries are defined once in
kbd-process-orchestrator/references/boundaries.md. Under VLBV (the method for
every phase; a deviation is a signed KBD-METHOD decision recorded in the phase's
method-context):
| Cadence concept | Becomes |
|---|---|
| Increment | Exactly one value phase with one adopted contract |
ready |
The contract amendment to implementationComplete |
candidate freeze |
B4 step 2 |
checkpoint build and functional run |
The build and run entries of the boundary packet (B4 step 3). In KBD mode checkpoint refuses a step whose argv is not a packet entry |
accepted / pending / blocked |
Derived from the canonical closure (report → canonicalOutcome): CLOSED with all PASS → accepted; open phase → pending; any FAIL, BLOCKED or NOT_EXERCISED → blocked, with the real verdicts shown |
review |
A pointer to the canonical decision id; it holds no approval of its own |
| Corrective iteration | A B5 repair under the same contract, or a new phase with a new contract |
work-ahead admit |
Requires the successor phase's adopted contract (successorPhaseId); without it the scope is exploratory and promote refuses it |
| Clock tick | B3: stops admitting new scope. Contract budgets are the hard limits; iteration duration is a planning target |
| Skill-pack refresh | Not shipped in mini (see the note above); never refresh procedure text while a bound phase is open |
Recover the method-context (scripts/kbd-method-context.mjs) and the latest
authorized supersession before choosing the next action; preserve original
evidence, candidate freshness, consumed budgets and unresolved effects. A task,
hour, commit, compiler problem or reviewer request never authorizes generated-code
verification of an incomplete phase. Resolve governing-policy conflicts before
dependent action without rewriting owner rules. Publication intervals do not
certify implementation or acceptance, grant release authority or create a
successor. These instructions do not claim universal tool interception.
Events and reports
Use hooks scaffold, hooks add, hooks list, hooks enable, hooks disable, hooks remove and deliberate hooks retry. Read JavaScript hooks before registration. Scripts have the user's privileges; registration is explicit trust, not a sandbox. Never send mail or other external effects without the configured authorization.
report shows tasks, changes and phases separately, carried scope, outcomes, artifact paths, overlapping wall time and unknown metrics. Use activity start/stop to record owned work spans explicitly. Reports distinguish gross, reopened and net progress, unknown timing and child costs. Never infer delivery from commits, a running agent, or an installer filename. See measurement and research.
Teams and project adapters
Use the selected .agent-team/project-routing.json / team manifest and the installed agent-team-creator contract. Assign disjoint owns, inputs and outputs. Use one implementer for isolated work, up to the configured maximum for independent stacks. One writer per shared build directory; one release metadata/site publisher. The lead performs optimization at checkpoints; it is not a continuous reviewer.
Refresh Compass for changed repositories about hourly when resources permit. Record stale/deferred status; do not launch a competing heavy build. Keep optional services optional.
For KBD/native goal binding and the Boss build-and-publication policy, read harness adapters. Completion of this skill never closes unfinished product work.
Progress Signals
Emit to plain response text (no tool call) at each delivery increment and child-phase boundary:
Starting delivery-cadence — <profile> increment <i> of <n>
Starting phase <i> out of <n>: <child-phase>
Completed phase <i> out of <n>: <child-phase>
Completed delivery-cadence — <profile> increment <i> of <n> (<accepted|pending|blocked>)
Acceptance and publication are reported separately; never report an increment as published because it was accepted.