UltraQA Task Card

Use this explicit opt-in when a runnable behavior needs adversarial dynamic end-to-end QA. Shared operating invariants live in templates/AGENTS.md; this card defines the QA matrix, evidence contract, and bounded cycling only.

When to use and inputs

• Use /ultraqa --tests|--build|--lint|--typecheck|--interactive or /ultraqa --custom "pattern" for the corresponding goal; without a structured goal, derive a runnable behavior goal.
• Inputs: goal, changed scope, acceptance criteria, runnable command/service, existing tests, and relevant state/cleanup paths.
• Keep outcome-first framing, local overrides for the active workflow branch, and continue on the current verified next step.
• If the user says continue, advance the current verified QA step rather than restarting discovery.
• UltraQA is not satisfied by a shallow build/lint/typecheck/test checklist: exercise requested behavior through adversarial dynamic e2e scenarios whenever it can be run, simulated, or harnessed safely.

Plan and scenario matrix

Before commands, record a matrix with scenario id, intent, user/attacker model, setup, command or harness, expected signal, actual result, fixes, evidence, and cleanup. Include a normal path and relevant hostile classes: