Check every path through a user flow
Drawing a user flow, such as a booking, as a chart of steps. A program then tries every order of steps, including retries and delays, to find where the user flow breaks.
Konstantin's verdict: Trial
pstack is a free set of ready-made instructions for coding agents, called skills. A developer who posts as poteto on X shared it. One skill finds bugs in a user flow. I tried it in October.
An agent draws the user flow as a plain-language chart. It shows each situation a user can be in and the events that move them on. A small program then tries every order of events, including retries and events at the same time.
My first chart was of a user flow that sends messages. The program found 6 flaws in its design. Then my agents checked four user flows at Kaufmann Health, my therapist-matching company. The program found 16 bugs a user could hit. The fixes shipped in the next release.
I can read the chart without the code. So bugs show up before users hit them.
What moved
On other radars
No community radar places this yet.
Sources
Share and embed
Makers: show where your product sits. The badge updates when the radar does.
Share this entry
Also in Practices · Trial
- Give agents narrow keysGiving each agent the narrowest access key and spending limit that does the job. One mistake or breach then reaches little.
- Guardrails, not manual reviewYou set the tests and limits once. Then agents ship without you checking each result.
- Let agents reach you by pushAgents bring questions and results to you, by text message, phone call or podcast, instead of leaving them in notes you must open.
- Pick a direction before agents build creative workFor creative work, agents first show several storyboards or directions. You pick one, then they build a rough version for fast feedback before any polish.
- Scheduled agent runsAgents run on a schedule and work through your inbox and task board. They fix what they can. You get only the decisions.