Ultraqa

This is a Hermes-native ultraqa workflow skill.

Why This Exists

ultraqa exists because behavior that passes its own tests can still fail under inputs and conditions nobody wrote down: it turns the changed behavior and known risks into hostile scenarios, records each one's observed pass or fail apart from any proposed fix, and hands fixes to the selected coding executor.

Do Not Use When

• Exploratory bug-hunting across a web app with no changed behavior to attack; on Hermes, use the bundled dogfood skill when it is available, and bring a finding back here as a scenario to reproduce.
• Judging whether a rendered page, image, or terminal frame looks right across viewports and states; use omh-visual-qa.
• Confirming that a finished change meets its acceptance criteria with the smallest proving check, when no hostile scenarios are wanted; use omh-verification-gate.

Examples

Good example: