agentsclimarketplace

Owner boundary triage

Skill Gesondian/ai-collab-governance-skills/skills/owner-boundary-triage

Hermes Loop Engineering skills for self-improving AI delivery governance.

Install
npx -y skills add Gesondian/ai-collab-governance-skills --skill owner-boundary-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when an AI must decide whether a failure belongs to a feature owner, shared capability owner, data owner, environment owner, or verifier.

SKILL.md

2.5 KB, 488 tokens by cl100k_base, as published. Nobody here has run it

Owner Boundary Triage

Core Principle

Owner conclusions require both reproduction breadth and mechanism attribution. A shared-looking source file is not proof that every consumer belongs to the shared owner.

Required Signals

  • Where the failure reproduces.
  • Where it does not reproduce.
  • Which mechanism appears responsible.
  • Which owner controls that mechanism.
  • Which consumers are affected.
  • Which evidence is missing.

Triage Flow

  1. Define the failing behavior in one sentence.
  2. Map reproduction breadth:
    • single route or surface,
    • multiple consumers of one capability,
    • all consumers of a shared capability,
    • data-source-specific,
    • environment-specific.
  3. Attribute mechanism:
    • feature composition,
    • shared component,
    • data schema,
    • permissions,
    • environment or harness,
    • acceptance wording.
  4. Assign owner only when breadth and mechanism agree.
  5. If they do not agree, return owner_boundary_unclear with the smallest next check.

Verdict Vocabulary

VerdictUse When
feature_ownerFailure is isolated to a feature composition or route-specific integration.
shared_capability_ownerFailure reproduces across consumers and mechanism is in the shared capability.
data_ownerFailure depends on data schema, lifecycle, or seed shape.
environment_ownerFailure depends on setup, harness, browser, network, or fixture availability.
verifier_ownerFailure is in the evidence, receipt wording, or acceptance procedure.
owner_boundary_unclearReproduction breadth or mechanism attribution is insufficient.

Output Contract

verdict:
failure_summary:
reproduction_breadth:
mechanism_attribution:
excluded_owners:
missing_checks:
next_owner:
return_gate:
return_owner_on_fail:

Common Mistakes

  • Assigning a shared owner because code lives in a shared folder.
  • Assigning a feature owner because the bug was first seen on one page.
  • Ignoring negative reproduction evidence.
  • Treating verifier wording mistakes as runtime defects.
  • Asking one owner to fix another owner's missing evidence.

Minimum Owner Claim

Use the narrowest owner conclusion that the evidence supports. If one more reproduction check would change the owner, do that check or return owner_boundary_unclear.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.