# Replay User Flows

Turn a user journey you just clicked through into a saved regression check that re-runs...

- Repository: https://github.com/reticlehq/reticle (1299 stars)
- Category: Testing
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add reticlehq/reticle --skill replay-user-flows -g -a claude-code -y`
Codex: `npx skills add reticlehq/reticle --skill replay-user-flows -g -a codex -y`
Cursor: `npx skills add reticlehq/reticle --skill replay-user-flows -g -a cursor -y`
Gemini CLI: `npx skills add reticlehq/reticle --skill replay-user-flows -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add reticlehq/reticle`

## Description

Turn a user journey you just clicked through into a saved regression check that re-runs deterministically, with no model in the loop and no test code to write. Use when you have driven the same flow twice, when the user wants regression coverage without a Playwright suite, when a refactor needs proving against every existing journey, or when re-verifying by hand is costing a full drive every time.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Record a journey once, re-verify it forever

Exploring an app to find a journey is the expensive part, and re-driving it with a model pays that cost again on every change. **Reticle flows** pay it once: the journey is saved with semantic anchors and replayed deterministically afterwards.

Needs Reticle wired in the project. Not set up? Follow the [`reticle`](https://github.com/reticlehq/reticle/blob/main/skills/reticle/SKILL.md) skill: it installs Reticle, asks the user before `init` changes the app's files, and proves one flow.

## Record

You do not have to ask. **A drive is saved as a flow automatically** when the session ends, written to `.reticle/flows/`. **Commit it**: any agent on the repo can then replay it.

What decides whether it is worth committing is how you drove it. A step keeps a consequence only when you declared one, so drive the golden path like this:

```
reticle_act_and_wait({ sessionId, ref, action: "click", until: { kind: "signal", name: "task:created" } })
```

That step replays as a test. A bare `reticle_act` saves a click with nothing to prove, and replays green through any regression.

To name a flow deliberately rather than take the automatic one, `reticle_record` and `reticle_flow_save` do it through `reticle_run { tool, args }`. Neither is advertised, and neither needs to be: `reticle_run` is on the default surface and dispatches to any registered tool by name. `RETICLE_ADVERTISE_ALL_TOOLS=1` advertises them outright, under older, unmerged tool names. Do not set it for an agent: the calls in this skill use the default names.

Annotate the business outcome, not just the clicks, so a replay proves the journey _achieved_ something. Extended surface, like the two above:

The rest: https://github.com/reticlehq/reticle/blob/HEAD/skills/replay-user-flows/SKILL.md