references/worked-example.md

MANDATORY: Before accepting any rationalization for approving without full verification, consult

references/rationalization-refutation.md

. Every common excuse is catalogued with a counter-argument and the correct action.

• User runs

  /review

  command (first stage)
• Task implementation is complete
• Need to verify spec compliance before quality review
• Subagent reports task completion

• State file path (preferred) OR design/plan paths
• Diff output from

  exarchos_orchestrate({ action: "review_diff" })

  (context-efficient)
• Task ID being reviewed

• Reads state file to get artifact paths
• Uses diff output instead of reading full files
• Runs verification commands
• Generates report
• Returns verdict to orchestrator

1. Generate diff:

   exarchos_orchestrate({ action: "review_diff", worktreePath: "<worktree-path>", baseBranch: "main" })

2. Pass diff content in the subagent dispatch prompt
3. Include state file path for artifact resolution

1. Receive diff content from dispatch prompt (do NOT re-generate)
2. Read state file for design/plan artifact paths
3. Run verification commands against the working tree
4. Return structured JSON verdict

• Evaluation strategy:

  exarchos_orchestrate({ action: "runbook", id: "review-strategy" })

  to determine the review approach based on diff scope, prior fix cycles, and review stage.

• The complete integrated diff (main...feature/integration branch)
• All changes across all tasks in one view
• The full picture of combined functionality

• Cross-task interface mismatches
• Bugs not visible in isolation
• Combined behavior vs specification

• Functional completeness
• TDD compliance
• Specification alignment
• Test coverage

• Code style
• SOLID principles
• Performance optimization
• Error handling elegance

1. Create fix task with specific issues
2. Dispatch to implementer (same or new)
3. Re-review after fixes
4. Repeat until PASS

// Return to implementer
Task({
  model: "opus",
  description: "Fix spec review issues",
  prompt: `

1. Missing rate limiting implementation
   • Add rate limiter middleware
   • Test: RateLimiter_ExceedsLimit_Returns429
2. Email validation incomplete
   • Add MX record check
   • Test: ValidateEmail_InvalidDomain_ReturnsError

• All tests pass
• Coverage >80%
• All issues resolved ` })

undefined

1. Classify as "cross-task integration"
2. Create fix task specifying ALL affected tasks
3. Dispatch fix to implementer with context from all affected tasks
4. Mark original tasks as blocked until cross-task fix completes

action: "set", featureId: "<id>", updates: {
  "reviews": { "spec-review": { "status": "pass", "summary": "...", "issues": [] } }
}

action: "set", featureId: "<id>", updates: {
  "reviews": { "spec-review": { "status": "fail", "summary": "...", "issues": [{ "severity": "...", "file": "...", "description": "..." }] } }
}

Important: The review value MUST be an object with a

status

field (e.g.,

{ "status": "pass" }

), not a flat string (e.g.,

"pass"

). The

all-reviews-passed

guard silently ignores non-object entries. Accepted statuses:

pass

,

passed

,

approved

,

fixes-applied

.

@skills/workflow-state/references/phase-transitions.md

• review

  →

  synthesize

  requires guard

  all-reviews-passed

  — all

  reviews.{name}.status

  must be passing

• review

  →

  delegate

  requires guard

  any-review-failed

  — triggers fix cycle when any review fails

1. Verify

   reviews["spec-review"].status === "pass"

   in workflow state (all tasks passed)
2. If not: "Spec review did not pass, cannot proceed to quality review"

Guard shape: The

all-reviews-passed

guard requires

reviews["spec-review"]

to be an object with a

status

field set to a passing value (

pass

,

passed

,

approved

,

fixes-applied

). Flat strings like

reviews: { "spec-review": "pass" }

are silently ignored and will block the

review → synthesize

transition.

1. Record results — the reviews value MUST be an object with a

   status

   field, not a flat string:

   exarchos_workflow({ action: "set", featureId: "<id>", updates: {
     reviews: { "spec-review": { status: "pass", summary: "...", issues: [] } }
   }})

2. Output: "Spec review passed. Auto-continuing to quality review..."
3. Orchestrator dispatches quality-review subagent immediately

Gate events: Do NOT manually emit

gate.executed

events via

exarchos_event

. Gate events are automatically emitted by the

check_review_verdict

orchestrate handler. Manual emission causes duplicates.

1. Record results with failing status and issue details:

   exarchos_workflow({ action: "set", featureId: "<id>", updates: {
     reviews: { "spec-review": { status: "fail", summary: "...", issues: [{ severity: "HIGH", file: "...", description: "..." }] } }
   }})

2. Output: "Spec review found [N] issues. Auto-continuing to fixes..."
3. Auto-invoke delegate with fix tasks:
   typescript

   [Invoke the exarchos:delegate skill with args: --fixes <plan-path>]

• Use the integrated diff (

  exarchos_orchestrate({ action: "review_diff" })

  ) instead of reading full files — reduces context by 80-90%
• Review per-task when the combined diff exceeds 2,000 lines
• Run TDD compliance check (

  exarchos_orchestrate({ action: "check_tdd_compliance" })

  ) in parallel with spec tracing