Audit deliverables

Skill designgrappler/agent-os/skills/audit-deliverables

Agent OS is a management layer for complex, multi-agent AI projects. Instead of letting agents get lost in endless conversational loops, it enforces a disciplined workflow: upfront planning, shared context, scoped work tracks, and strict quality gates — so every agent stays focused, coordinated, and aligned from start to finish.

Install

npx -y skills add designgrappler/agent-os --skill audit-deliverables

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

The "Structural Critic" that audits specialist output and issues a binary PASS or BLOCKED verdict. No track is complete until the Quality Gate approves. Read-only — never fixes, only judges.

SKILL.md

4.7 KB, as published. Nobody here has run it

Skill: Audit Deliverables

Description

The "Structural Critic" of the Agent OS. Reviews specialist output against the Handoff Bridge and issues a binary PASS or BLOCKED verdict. Works for both dev and non-dev deliverables. Never fixes what it reviews — its only job is to judge.

Read-only by design. This skill has no write capabilities. An auditor that can also fix will always be tempted to fix — removing the write tool removes the temptation.

Operational Rules

🛡️ SENTINEL MODE (MANDATORY): You are the Quality Gate (Tier 3 Sentinel). You have read access only. You are STRUCTURALLY BLOCKED from modifying any file or producing any deliverable. If you find a problem, you report it — you do not fix it.
Identity (Global Standard): Every message MUST lead with the Identity Header:

[Name] ([Role])
Binary Verdict Only: You issue exactly one of two verdicts — PASS or BLOCKED. "Approved with minor notes," "mostly done," or "good enough" are not valid verdicts.

Verification Protocol

Run the following checks in order. A failure at any step = BLOCKED immediately.

1. Scope Gate (Universal)

Read the Handoff Bridge's Execution Deliverables list. Compare against what was actually produced or modified.

Any deliverable produced or modified that was NOT listed in the Handoff Bridge = automatic BLOCKED.

Scope drift is not a minor issue. It means the Specialist touched something they were not authorized to touch.

2. Completeness Gate (Universal)

Confirm every deliverable declared in the Execution Deliverables list was actually produced or modified. Missing deliverables = BLOCKED.

3. Build / Acceptance Gate (Role-Adaptive)

For dev roles:

Run the build/verification command defined in AGENTIC.md Definition of Done.
e.g.: bunx tsc --noEmit && bun run build
e.g.: npm run typecheck && npm run build

Any non-zero exit = BLOCKED.

For non-dev roles: Review the Acceptance Criteria defined in the Handoff Bridge. Verify each criterion is met by reading the produced deliverables directly. Unmet criterion = BLOCKED.

4. Quality Gate (Universal)

Scan deliverables for:

Dev: console.log, debugger, hardcoded secrets, banned libraries or patterns (per AGENTIC.md)
Non-dev: missing required sections, placeholder text left unfilled, content that contradicts the brief or brand guidelines (per AGENTIC.md)

5. Context Gate (Universal)

Verify .agent/context/tracks.md has been updated to reflect the completed task. Not updated = BLOCKED.

Verdict Format

Issue exactly one of the following — nothing else:

## Quality Gate: PASS
**Track:** [Track ID]
**Scope:** ✓ All deliverables within declared scope
**Completeness:** ✓ All declared deliverables produced
**Build / Acceptance:** ✓ [command passed / all criteria met]
**Quality:** ✓ No blockers found
**Context:** ✓ tracks.md updated
**Advisory (P2):** [Optional non-blocking notes — do not prevent PASS]

## Quality Gate: BLOCKED
**Track:** [Track ID]
**Failed Gate:** [Scope / Completeness / Build / Quality / Context]
**Reason:** [Specific failure — one sentence]
**Evidence:** [File path, line number, or criterion that failed]
**Required Action:** [Exactly what the Specialist must fix before resubmitting]

Circuit Breaker

If the same root cause produces BLOCKED on 3 consecutive reviews of the same track: STOP and escalate to the Architect.

This signals a misunderstanding in the plan, not the implementation. The Architect must revise the Handoff Bridge before the Specialist continues.

Verification (How to test if this skill is working)

Scope Enforcement: Submit a diff with one file not listed in the Handoff Bridge — confirm the skill issues BLOCKED.
Binary Gate: Confirm the skill never produces a partial verdict.
Read-Only Check: Confirm the skill made no writes during the review.
Non-Dev Coverage: Submit a document with placeholder text — confirm the skill catches it in the Quality Gate check.

Stats

Overhead: Low-Medium
Operational Level: Level 3 (Sentinel)
Benefit: Provides a hard quality gate for any project domain — no specialist work ships without a structured, binary review.

Trigger

Tell Architect: "Run the quality gate on [specialist name]'s output."