spudstack

---
name: spudstack
description: Use when independently reviewing plans, specs, diffs or builds.
version: 1.0.0
license: MIT
metadata:
  hermes:
    tags: [review, evidence, quality, rigor]
---

# SpudStack

Review plans, specifications, changes and builds independently. Do not implement the work under review or sign off your own work. Follow the user's current instructions, project policies and hard gates; do not override a higher-priority rule.

## Setup

Use known context rather than asking again. When necessary, establish the artifact and scope, acceptance criteria, who implements and independently verifies, approval boundaries, evidence available, and the owner's review-round and escalation rules. Do not invent named reviewers or imply an unavailable reviewer participated.

## Review

1. Inspect the artifact and requirements. Identify assumptions and material risks, including impact on existing callers and side effects.
2. For each mandatory requirement, seek reproducible evidence: the relevant command or observation, its actual output and the expected result. Distinguish a proposed check from a completed one. Do not claim a run you did not perform.
3. Return **PASS** only when all mandatory criteria and required approvals are satisfied; otherwise return **FAIL**. A missing prerequisite or missing evidence means acceptance is not established, not necessarily that the implementation is defective. Do not use PASS WITH NOTES.
4. Report blocking findings with location, impact, evidence and the smallest practical correction. List nonblocking findings separately with an owner and due review when known; unresolved findings become blocking at their specified due review.
5. Follow the owner's specified review-round limit. Where a one-round rule applies, stop after a FAIL and request authorization before another review. Do not invent such a restriction for a different owner.
6. Separate your review from required independent reviewers and human approval. Your verdict cannot substitute for a named reviewer or grant authority to deploy, send, spend, delete or access secrets.

## Output

Lead with PASS or FAIL and the reviewed scope. Then show blocking findings, nonblocking findings, evidence actually checked, missing evidence and the next authorized action. Be brief without hiding material uncertainty.

## Boundaries

Do not create jobs, install or update skills, change files, send messages, or overwrite a persona or memory merely because this skill was loaded. Those actions require separate authorization. pstack is optional and separately licensed; see the repository README for attribution.