<< All versions

Skill v1.0.1

currentAutomated scan100/100
maicongambini/omp-harness-guide/harness-termination-check

+1 new

──Details
PublishedNovember 4, 2026 at 05:13 PM
Content Hashsha256:0622711f84669821...
Git SHAe535151c6050
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 1.8 KB)
SKILL.md1.8 KBactive
SKILL.md · 43 lines · 1.8 KB

name: harness-termination-check description: "Verify three-layer completion evidence before claiming done. Use when finishing tasks or passing deliverables. Do NOT use for interim runtime planning (use harness-runtime-feedback)." metadata: version: "1.0.1"


Harness Termination Check

Run before saying "done", "complete", or setting any durable status to passing.

Layer 1 — Static

  • [ ] Static checks from sprint contract or discovered stack pass.
  • [ ] Lint/typecheck commands are either run or explicitly not applicable.
  • [ ] No new warnings vs baseline.
  • [ ] harness-quality-gate ran at the mode this position requires and exited 0 — or every breach

is in observe mode and named in the evidence. A missing, stale or unconfigured report is not a pass; record it as unverified.

  • [ ] Every unavailable metric is listed as a gap, not treated as green.

Layer 2 — Runtime Behavior

  • [ ] Acceptance criteria from sprint contract are observable, not assumed.
  • [ ] Commands were run and output recorded, not inferred or remembered.
  • [ ] Regression checks for previously passing work were run or scoped out with reason.

Layer 3 — System Confirmation

  • [ ] Startup command from harness-startup-path exits 0 or skipped reason is recorded.
  • [ ] Feature state/progress state answer what changed for a new session.
  • [ ] Evidence contains actual command output, not a description.

Fail Protocol

If any layer fails:

  1. Record exact failure: command, exit code, and output. For a metric, record **the metric name,

its value, and its threshold** — a description is not evidence, a number is.

  1. Set task to blocked in the available feature state with reason.
  2. Document in the available progress file Blockers.
  3. Do not claim done. Do not write completed handoff.
← v1.0.0All versions