ProductTests your live product and says pass or fail
Product QA tester
It signs up to your product with its own email address and walks every screen each weekday, without touching real data, then tells you what shipped, what disappeared, what broke with steps and screenshots, and which product calls need you. When a feature is ready, it turns your scope or spec into an acceptance checklist, runs it on the live deploy and gives a plain pass, fail or blocked, with ship blockers kept apart from warnings. It never fixes code, files tickets in your name, or uses your account or a customer's.
- Works with
- GitHubClickUpSlackNotion
- Recommended model
- Claude Sonnet 5.5
- Skills
- 6
What it does
- Signs up and keeps its own test account, reading verification emails in its own inbox
- Walks every screen each weekday without submitting, paying, inviting or deleting anything
- Reports what shipped, what disappeared and what broke, with repro steps and screenshots
- Turns a scope or spec into an acceptance checklist with ship blockers and warnings
- Runs the checklist on the live deploy and says pass, fail or blocked, with evidence per item
- Re-runs the ship blockers after each merge or deploy and stays quiet when nothing changed
The skills it brings
Playbooks the mate follows when the job calls for them. You can read and edit every one after adding it.
/pqa-setuppqa-setupUse on the first conversation, or when the person changes the product, the surfaces to watch, the shipped-work signals or where bugs go, to collect the basics and end with a first baseline walk.
/pqa-test-accountpqa-test-accountUse to sign up your own test account with your own email address, catch its verification emails in your inbox, sign back in when signed out, and check you are in the right account before every walk or run.
/pqa-product-walkpqa-product-walkUse to walk the person's live product in the test account, either as the first baseline map of every surface or as the daily walk that compares each surface with the map and the shipped-work signals. Non-destructive only.
/pqa-rundownpqa-rundownUse after a product walk to send the rundown (shipped, unshipped, broke, decisions), hand bugs to wherever the person wants them, and record the product calls the person makes.
/pqa-acceptance-packpqa-acceptance-packUse when the person or a product mate hands over an approved scope, spec or ticket, to turn it into an acceptance checklist where every item is checkable on the live product and marked ship blocker or warning.
/pqa-acceptance-runpqa-acceptance-runUse when a feature is said to be done, before a ship, or after a merge or deploy, to run an acceptance pack on the live product and report pass, fail or blocked with evidence for every item.
Things to ask it
Walk our product now: …Turn this spec into an acceptance checklist: …Run the checklist on the live siteWhat broke this week?