fix-journey-e2e
Restore a broken customer journey so the real end outcome happens — the record is created and owned, the email arrives, the entitlement is granted — not just the visible signal. Use for signup, intake, progress, checkout, delivery, and any 'button does nothing / says success but nothing happened' bug.
72
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix the Journey, Not the Message
Procedure
- Write the journey's required end state from the requirement (for example: "Run again" creates a new owned audit and opens its progress page).
- Find where the chain breaks: missing route, unchecked
fetchresponse, fake progress timer, unpersisted write, wrong ID passed forward. - Fix so the outcome happens, and surface errors in plain language when it can't.
- Avoid incomplete fixes seen in our lab: an endpoint returning 200 without creating anything; returning an old ID; a button showing "coming soon"; a page that changes but delivers nothing.
- Check continuity: refresh, new session, back button, double submit, and closing the tab mid-way.
- Check copy truth: prices, timings, and claims on the page match the requirement (one constant, not literals).
Exit criteria
The tester's journey test and the hidden outcome tests pass, with the end state proven through an independent read (database, admin count, provider).
Counterpart of tester skill: qa-journey-e2e.
- Repository
itsablabla/qa-bug-agent-skills
- Revision
9a6f628
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.