Flow Friction Audit

Drive a real, running flow through the browser and turn what happens into friction evidence a designer can act on. The value is the middle: most UX tooling either drives a browser (no judgement) or critiques a design (no live behaviour). Do both — observe the running product, convert each interaction into named evidence, agree what those problems are, and only then shape fixes against them.

Evidence and agreed problems are the load-bearing output; they stand on their own even if nothing is designed. impeccable owns the critique and sharpens the directions — it doesn't decide what's wrong.

Two modes, one skill

The pipeline splits at the 3b alignment gate, and each half is invoked separately. Running all five stages in one pass makes a single audit expensive, and it leaves the agreed problem space living only in that conversation — so the next run re-derives what's wrong instead of designing against it.

• audit — stages 1 to 4. Walk the flow, score it, agree the problems, write the alignment doc and findings.md. Ends at alignment; no design work.
• shape — stage 5. Take an already-aligned problem set and produce researched fix directions. Re-runnable: the problem space is settled, so each invocation spends its budget on ideas rather than rediscovering the friction.

Route on entry: the user points at or names an aligned-problems doc → shape. Otherwise → audit, from stage 1. Never go looking for a doc the user didn't name — auto-discovery is the same mistake as reading a prior audit (Fresh runs): it quietly makes someone else's stale problem set the frame for a flow you haven't looked at yet.

Prerequisites