gustavo-meilus/superpipelines / plugins/superpipelines/skills/pipeline-spec-reviewer-protocol
pipeline-spec-reviewer-protocol
VerifiedLoaded by the pipeline-spec-reviewer agent to perform Stage 1 spec-compliance review.
Pipeline Spec Reviewer — Operational Protocol
Q8 — Self-Skepticism Preamble (Inline Dispatch Only)
When the active platform_profile.capabilities.dispatch_mechanism == "inline" (Tier 2 — Cursor / Windsurf / Cline), this protocol runs in the same agent context that wrote the code under review. Structural isolation is unavailable; the reviewer and the writer are one agent. To soft-compensate for the lost assumption-blindness defense, apply this preamble:
Inline-review self-skepticism directive. You are reviewing your own prior work in this same session. Your context already contains the reasoning that produced the code under review — that reasoning will bias you toward accepting it. Counter the bias explicitly:
- Treat every acceptance criterion as a binary check; do not extrapolate intent from the spec to cover gaps in the implementation.
- When in doubt about whether an AC is met, flag rather than pass. The default is FAIL; PASS requires affirmative evidence.
- List the specific lines / files that satisfy each AC. If you cannot point to lines, the AC is unverified.
- Reject any "the spirit of the AC is met" reasoning. Spec compliance is mechanical, not interpretive.
This preamble is unnecessary on structurally-isolated tiers (1, 1b, 1d) where the reviewer is a fresh agent context.
Workflow
2. VERIFY COMPLIANCE
Evaluate the executor's output against each AC:
- MET: AC is fully satisfied by the output.
- UNDER-BUILD: AC is missing or partially satisfied. Triggers a FAIL.
3. AUDIT SCOPE CREEP
Check every modified file for over-build:
- File Allowlist: Were any files modified outside the task's
fileslist? - Unrequested Features: Are there new functions, helpers, or features not defined in the spec?
- Note: "Useful extras" are treated as contract violations. Triggers a FAIL.
4. EMIT VERDICT
- PASS: All ACs met and zero over-build detected.
- FAIL: Any instance of under-build or over-build.
Rationalization Resistance
<rationalization_table>
| Excuse | Reality |
|---|---|
| "Useful over-build" | Creep violates the contract parallel workers depend on; FAIL always. |
| "Mostly met" | Mostly = Under-build. Functional correctness is not a gradient. |
| "Trust the executor" | Executors cannot review themselves. Verify every AC against the actual output. |
| </rationalization_table> |
Reference Files
${CLAUDE_PLUGIN_ROOT}/skills/sk-write-review-isolation/SKILL.md— Isolation protocol.${CLAUDE_PLUGIN_ROOT}/skills/sk-claude-code-conventions/SKILL.md— Formatting rules.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |