Ultraqa

Ultraqa

This is a Hermes-native ultraqa workflow skill.

Why This Exists

ultraqa exists to keep verification work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.

Do Not Use When

• The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
• The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.

Examples

Good example:

• Prompt: $ultraqa test the setup wizard with hostile install paths, stale config, and missing PATH cases.
• Expected behavior: Generate adversarial QA scenarios, expected signals, observed results, and fix-or-retry routing.
• Why: The request asks for verification pressure and hostile scenarios.

Bad example:

• Prompt: ultraqa: treat casual chat or unaccepted work as if this workflow already produced verified results.
• Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing ultraqa.
• Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.

Completion Checklist

• The scenario, expected behavior, observed result, and pass/fail basis are named.
• Proposed fixes are separated from observed QA evidence.
• Missing or failed verification routes back to plan, fix, or a narrower test.

Recovery Notes

• If the expected behavior is unclear, route back to plan before running adversarial checks.
• If verification fails, return to fix or research with the failed signal instead of advancing.

Workflow Lane