oldhand-qa

Runs the QA panel for a change: turns the contract's acceptance and regression criteria into scenario cards (acceptance, the original failing case, neighbouring regressions, negative paths and messy real-world input), spawns one QA sub-agent per scenario to drive the real app through a browser, computer use, an API or a CLI, collects screenshots and response bodies as evidence, tallies pass, fail and blocked into the task ledger, and has the lead re-run the most important scenario itself. Use when the user says "QA this change", "run the QA scenarios", "make sure existing stuff still works", "try it with messy inputs", or after oldhand-review. Not for writing unit tests, reviewing a diff (oldhand-review) or deciding whether to ship (oldhand-ship). One stage of oldhand; for a whole ticket or fix, use oldhand.

License

MIT