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.
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.
Turn an existing brief into a proposal you can review
Bring the ticket, PRD excerpt, or rough notes you already have. Have your coding agent propose the change, then compare its interpretation with your original request in Pathmode.
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.
Pressure-test a spec against your strategy before the team commits
Compare the proposal with workspace strategy, product boundaries, and constitution rules. Record why this work deserves priority before approving the build.
Turn scattered customer signal into one prioritized spec
The signal is real, but it's in twelve places: a sales call, two Slack threads, a churn email, your own notes. Capture it all in Pathmode, judge it one signal at a time, and end with a spec whose claims say what backs them.
Go from a vague founder-ask to a testable goal
Turn a rough request into a clear problem, observable outcomes, and a proposal your team can review before implementation.
Convert a Slack thread into an evidence item
Customer feedback dies in Slack. Paste a thread, get a structured signal with the quote, the context, and the source, sitting Unreviewed in the Evidence Inbox until you judge it.