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.
Review and correct an agent's proposal before it builds
Follow Maria and Sam from a cancellation proposal through correction, approval, and a later cleanup request that uses the same paid-access decision.
Hand the authorized proposal to your coding agent
Carry the product manager's corrections and revision authorization into Claude Code, Cursor, or Codex, then check the implementation against the agreed intent.
Generate a PR description from the linked IntentSpec
The agent that built the work already holds the spec it built against. Have it write the PR description from that spec: objective, outcomes, verification criteria, and edge cases, so reviewers see intent and tests in the same place.
Run a deterministic preflight before your agent starts building
Six calibrated checks, no model call, no account. The preflight reads your intent.md, names the exact gates that block it, and the same spec always gets the same verdict. Repair happens one question at a time, with readiness kept separate from approval to build.
Let your agent pull intent live with the Pathmode MCP server
Stop pasting specs into the agent. With a connected workspace, Claude Code preflights the repo's intent.md, reads the full execution context, stops for open PM requests and for a person to authorize the exact revision, then hands the pull request back for a diff-graded verdict.
Verify the pull request against the spec it was built from
Name the PR and Pathmode reads the diff from GitHub itself, grading every outcome, constraint, and edge case against what the code actually shows, with citations. A summary of your own work is weaker evidence, and the verdict says so.
Let a coding agent correct the spec it's building from
An agent building your spec discovers the spec was wrong. Instead of burying that in a PR comment, it records a finding that rides into the next agent's prompt and flips the falsified check to failing, then proposes the exact correction for a person to accept. The loop converges, and a human closes it.
Capture a customer call as structured evidence
You just got off a call full of signal. Before it evaporates, drop the transcript in. Pathmode pulls out the quotes and tags each by type and severity, and they wait Unreviewed in the Inbox until you judge them. No synthesis doc required.
Anchor every outcome to user evidence
Stop writing specs from imagination. Every claim in a Pathmode spec shows what backs it and who judged it, so a year from now you can still answer 'why did we build it that way?'
Audit a draft spec for missing edge cases
Compare a draft proposal with its request, identify missing failure cases, and review the agent’s corrections before approving implementation.
Spot the conflict between two stakeholder requests
Keep both stakeholder requests visible, name the conflicting behavior, and review an explicit decision before the coding agent implements it.
Turn 30 support tickets into a prioritized spec
Import a CSV export of recent tickets. Every row lands in the Evidence Inbox as an unreviewed signal, and you decide which ones become reviewed backing for an exact claim in your spec.