workflow-reviewer

Reviews pipeline phase handovers against methodology exit criteria and returns approve, reject, or escalate verdicts.

5|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/civitas-cerebrum/achilles --skill workflow-reviewer-civitas-cerebrum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-reviewer
Source: https://github.com/civitas-cerebrum/achilles/tree/main/skills/workflow-reviewer
Command: npx skills add https://github.com/civitas-cerebrum/achilles --skill workflow-reviewer-civitas-cerebrum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous QA pipelines can silently compress scope at phase transitions — skipping phases, stopping early, or accepting incomplete deliverables. This Skill gates every phase, pass, and cycle transition of the Achilles onboarding, coverage-expansion, journey-mapping, and perf-onboarding pipelines by reviewing the closing handover against canonical methodology exit criteria before the orchestrator may advance. ## Core Features & Use Cases - Transition gating: Dispatched as a subagent at every phase (1-8), coverage pass, journey-mapping cycle, and perf-onboarding phase/pass boundary, returning a structured verdict of approve, reject, or escalate per the workflow-reviewer.schema.json contract. - Checklist-driven review: Converts each methodology section into yes/no checklist items with evidence and methodology references, covering scaffold, groundwork, happy-path, journey-mapping, coverage, bug-discovery, secrets-sweep, report, and k6 performance phases. - 3-cycle reject cap and skip authorization: Enforces a maximum of three review cycles per unit before escalating to the user, and acts as the only legitimate path for approving phase skips or early stops when an explicit authorizer is present. - Use Case: After Phase 3 of an onboarding run completes, the orchestrator dispatches workflow-reviewer-phase3 with the ledger, handover envelope, and deliverables; the reviewer verifies one passing spec per primary journey and the discovery-draft sentinel, then returns an approve verdict or surgical fix instructions. ## Quick Start Dispatch the workflow-reviewer-phase3 subagent with the onboarding ledger, the Phase 3 methodology section, and the closing handover envelope to verify the happy-path exit criteria before advancing.

Frequently Asked Questions about workflow-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an onboarding phase before advancing to the next one?

Dispatch the workflow-reviewer-phase<N> subagent with the onboarding-status.json ledger, the methodology section for that phase, the produced deliverables, and the closing handover envelope. It returns approve, reject with surgical fix instructions, or escalate after three rejects.

What verdicts can the workflow reviewer return?

The reviewer returns one of three verdicts: approve lets the orchestrator advance, reject triggers a surgical fix and re-dispatch of the same reviewer, and escalate surfaces all three reviewer returns to the user after the third consecutive reject.

Can the workflow reviewer approve skipping a phase or stopping early?

Yes, but only when the dispatch brief carries an explicit authorizer, such as a verbatim user quote or a documented structural exception. Self-imposed reasons like session length, budget, or inferred user preference are rejected.

Does the workflow reviewer edit code or write specs?

No. The reviewer is a read-only critic that checks deliverables against methodology exit criteria. It never edits code, writes specs, or dispatches further subagents; fixes are executed by the orchestrator.

What happens after three consecutive reviewer rejects?

The third reject sets verdict to escalate and handover status to escalated-to-user. The orchestrator surfaces all three reviewer returns with findings and attempted fixes to the user, and the pipeline ledger status becomes blocked.