qa

/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.

3.5. Acting verification fan-out (behavior-bearing artifacts): a text judge can be fooled by a hopeful log line. Use the active runtime's orchestrate_subagents capability to launch, together, one probe child per acting modality the runtime exposes: a process probe (run_shell: run the command or app or smoke commands with bounded timeouts, capture exit codes and real output), a browser probe (HTTP services and web UIs: load them, exercise the primary flows, capture rendering and console/network errors), a computer-use probe (GUI/TUI: drive it like a user, screenshot observed states), and an artifact probe (inspect_code: declared files exist with real content, not placeholders). Each probe returns structured evidence only (commands, observed effects, screenshots/paths, pass/fail per behavior) and covers the applicable adversarial classes the QA tool lists. Skip a modality only when its tools are absent or it is meaningless for the artifact, and say which were skipped and why. Await all probes and pass the merged evidence as reference; prefer observed behavior over source text as the artifact when they disagree.