PR story

Produce one cohesive user-story narrative for the current branch. Output goes to tmp/pr-story.md. Do not summarize or report to the user after writing — they review the file directly.

Phase 1: Examine changes

Diff the branch against its base (committed + unstaged): git diff "$(git merge-base HEAD origin/main)"...HEAD and git status --short if needed.
Identify one primary user path to tell (e.g. send a single message). Do not weave parallel flows (blasts, API-only paths, verifications, etc.) into the story unless the user names a different path — save them for Notes instead.
Trace that path in code: follow calls in execution order, noting only files touched on this branch.

Phase 2: Outline

Before writing prose, sketch a short outline (mental or scratch — not delivered to the user):

Opening: who acts, where in the product, what triggers the flow
Middle: call chain in order, branch points (if paths for this invocation)
End: success path and failure path the user sees
Notes (sketch only): parallel entry points, shared infra, migrations, and flags worth a reviewer mention