How builders ship the right thing.
Follow a proposal from request to review, bring evidence into a decision, or prepare the handoff to your coding agent. Pick a workflow or role to find the relevant steps.
Catch the experience gaps in a spec before build
The happy path is in the spec. The empty state, the error, the slow connection, the screen-reader user — usually aren't. Review the spec from the experience side and add the states a coding agent will otherwise invent badly.
Decide what the team builds next
Use the Intents list to find pending reviews and missing outcome measurements, then compare the candidates and record why one should come next.
Turn a design rationale into outcomes engineers can verify
Carry the user result, design decisions, and supporting research into a proposal the engineer can verify without losing the reason behind the design.
Sequence work so agents have the dependencies they need
Check the prerequisites behind related intents, agree the build order, and hand the agent an authorized proposal based on contracts that are actually available.
Turn a usability test into a spec the team can build
Five sessions, a pile of clips, and a sinking feeling that it'll all live in a deck nobody opens. Capture the observations in Pathmode and walk out with a spec whose outcomes name the exact moments users struggled, and who judged that they count.
Find the friction pattern across 5 user interviews
Five interviews, five different stories, one pattern underneath. Capture the transcripts as signals, judge them one at a time, and the pattern shows up as the claim several independent sources back.