UltraQA Skill

Operating Contract

• Use outcome-first framing with concise, evidence-dense progress and completion reporting.
• Treat newer user updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.
• If the user says continue, advance the current verified next step instead of restarting discovery.
• UltraQA is not satisfied by a shallow build/lint/typecheck/test checklist. It must exercise the requested behavior through adversarial dynamic e2e scenarios whenever the target can be run, simulated, or harnessed safely.
• UltraQA is an adversarial review and evidence method: it designs scenarios, observes behavior, classifies results, and returns observations plus repair requests. The caller owns effects, fixes, lifecycle state, and verdicts.
• Under /exec, Exec runs the commands, harnesses, and cleanup and receives the repair requests; UltraQA never routes back into Exec. On a direct user request that needs a fix or state change, route it once to the existing skill://exec (step 6), with no new driver, CLI, or plugin.

[ULTRAQA ACTIVATED - ADVERSARIAL DYNAMIC E2E QA CYCLING]

Overview

UltraQA finds real behavior failures by combining normal verification commands with generated end-to-end scenarios, hostile user modeling, temporary harnesses when useful, and a structured evidence report. The workflow repeats observe → diagnose → request repair → re-observe the repaired revision until the goal is met, a bounded stop condition is reached, or a safety boundary blocks further execution. UltraQA originated as an OMX workflow; this generalized method keeps its scenario, cleanup, and stop discipline on any host.

Goal Parsing