observe-run

Observe Run

Run a command, then read the telemetry that run just emitted, and grade a stated behavioral claim against it.

A test asserts through a keyhole. A trace of the same execution exposes the whole thing: fan-out that went from 2 calls to 14, a retry that fired 5 times, an error swallowed into a 200, an N+1 query, a user ID landing as unbounded metric cardinality — none of which turns a test red. This skill closes that gap by giving the dev loop a fourth telemetry role this repo did not have: telemetry as verification evidence, read seconds after the run that produced it, rather than telemetry read as coverage, as yesterday's production exposure, or as a post-deploy confirmation.

This SKILL.md is a thin index. Detailed rules live in rules/*.md and load on demand.

---

Inputs

The inputs are a command plus an expectation set — nothing else.

Skill("observe-run")
  command:      <the command that runs the code under test>      # required
  expectations: <one or more behavioral assertions>              # required; by-construction ones are refused
  rung:         1 | 2                                            # optional; default resolved by rules/rungs.md
  run_id:       <string>                                         # optional; defaults to a generated dev.run.id
  caller:       <invoking skill or agent>                        # logging only

Return value is exactly one verify-behavior receipt, whose final line is [receipt] verdict: <confirms|contradicts|ambiguous|null> — or nothing at all when the self-skip gate below fires.

This skill has zero dependency on any aw artifact. It takes no worktree for granted, reads no plan artifact, and checks no acceptance-criteria ledger. It runs anywhere a command can run.

---

The self-skip gate

Before doing any work, resolve the repo's committed Observability Profile (<repo>/memory/observability-profile/INDEX.md, written by measurable setup — see skills/quality/measurable/rules/setup-profile.md) and check it names a dev run target (the field measurable setup now asks for — see Integration: measurable).