/ouroboros:qa

Fast single-pass quality verdict with actionable suggestions for any artifact: code, documents, API responses, test output, or custom content. For formal three-stage verification of an execution, use ooo evaluate.

ooo qa [file_path | artifact_text]
ooo qa                                     # recent execution output
/ouroboros:qa [file_path | artifact_text]

The QA Judge scores the artifact against a quality bar on Correctness, Completeness, Quality, Intent Alignment, and Domain-Specific dimensions:

Score	Verdict	Loop action
>= 0.80	PASS	done
0.40 - 0.79	REVISE	continue
< 0.40	FAIL	escalate

Instructions

Loading MCP tools (deferred-schema guard)

Ouroboros tools may be deferred, and a schema loaded on one turn can unload by the next. Immediately before each ouroboros_* call, load it with the active runtime's tool-discovery capability: "+ouroboros qa" for ouroboros_qa. A call whose schema is not loaded fails with "Invalid tool parameters". If the tool is already callable, discovery is a no-op and an empty result is expected. Use the fallback only when the tool is genuinely absent; this skill works without MCP setup.

QA steps

1. Artifact: a file path (read it with the active runtime's inspect_code capability), inline text, or else the most recent execution output; ask with ask_user if unclear.
2. Quality bar: the Seed's acceptance criteria when a Seed is in context, else the user's stated bar; otherwise ask "What does 'good' mean for this artifact?"
3. Artifact type: code, test_output, document, api_response, screenshot, or custom.