Turn a recording into a ticket or test

The same recording that shows a bug can become the ticket that tracks it and the test that keeps it fixed.

Write a ticket

prompt

Write a bug ticket for this Traceo recording:
- https://www.traceo.dev/82efc229a22f4ffd81

Include steps to reproduce, expected vs actual, the environment, and the errors and failed requests as evidence.

If the traceo-to-ticket skill is available, use it.

The agent writes a ticket you can paste straight into your tracker:

A short title naming what broke and where.
Steps to reproduce, from the recorded clicks.
Expected and actual behaviour, with the time it happens in the recording.
The environment, and the errors and failed requests as evidence.

With Linear, GitHub or Jira connected to your agent, it searches for a matching open ticket first and files a new one only after you confirm.

Write a test

prompt

Write an end-to-end test for this Traceo recording:
- https://www.traceo.dev/82efc229a22f4ffd81

Replay the user's steps with this project's own test setup.
If the recording shows a bug, the test should fail until the bug is fixed.

If the traceo-to-e2e skill is available, use it.

The agent uses the test setup your project already has, such as Playwright or Cypress, replays the recorded steps and asserts on the failure. For a bug recording, the new test should fail now and pass once the fix lands.

Recorded selectors such as div.flex.shrink-0 are hints. The agent prefers your test ids, roles and visible text, so the test does not break the next time styles change.

Setup

Both prompts need Traceo MCP connected. Install the Traceo skills for the best results.