Send product judgment to the repo.
Authorize the exact revision.
Product and design can request a change without operating Git. The repository agent applies it to intent.md, Pathmode shows the resulting diff, and a human authorizes the exact revision. Pathmode passes that current verdict to the implementation agent.
Read our manifesto: The Vibe Coding Hangover →
01 · Capture
Stop filing insights into the void.
Research dies in PDFs. Feedback dies in Notion pages. Pathmode turns raw signals (support tickets, quotes, observations, metrics) into structured Evidence Items that drive what gets built.
- Capture, then judge: Paste raw feedback and AI classifies it by type and severity: friction, quotes, observations, metrics, requests. Everything lands in the Inbox marked Unreviewed until a person reviews it.
- Products: Organize evidence by product area. Each Product carries a manifest with vision, constraints, and principles, so AI suggestions stay aligned.
- Start from assumptions: No research yet? Seed a Product with AI-drafted hypotheses. Every item carries an origin label, so assumption and observation never blur.
Cut settings drop-off from 73% to under 20%
reviewed by Maya, 12 Aug
Password change reachable in two clicks
reviewed by Maya, 12 Aug
Save completes on mobile Safari
2 signals waiting in the Inbox
The existing session model does not change
nothing anchored here
SSO users with no local password
AI-drafted, never becomes backing
02 · Shape
Bring a brief or an agent-written proposal.
Review the proposed objective, outcomes, constraints, and edge cases alongside the signals behind them. Decide what to keep, what needs a change, and what is still an assumption.
- Suggested until reviewed: In a brief draft, agent additions stay marked until you keep, edit, or remove them. Keep clears a marker; it does not create a permanent record of who accepted the claim.
- Backed claim by claim: Use as backing reviews a signal and anchors it to one exact claim in a single attributed action, so the objective, each outcome, each constraint, and each edge case reads Backed, Unreviewed, Assumption, or No evidence. The repository gets safe references; private customer material stays outside Git.
- Readiness gate:Deterministic checks catch a vague objective, an unobservable outcome, or a missing failure mode before an agent sees the spec. Evidence stays advisory: the machine flags what's absent, you judge what carries the decision.
Can't complete purchase on mobile
User reports that the payment button is unresponsive on iOS Safari. Tried clearing cache, same issue. This is the 5th report this week.
Users prefer the new nav
Actually wait — 6/8 participants struggled with the dropdown. Need to revisit this. @Jake thoughts?
"I just want to see my order status without logging in every single time. Why is this so hard?"
Pricing page shows wrong currency
Multiple reports from EU users. Prices show USD despite locale being set to DE. Unclear if this is a frontend or API issue.
Dashboard data doesn't match reports
Enterprise customer threatening to churn. Revenue numbers on dashboard are off by ~15% compared to exported CSV.
P3 abandoned the task after 4 minutes. Said "I don't understand what this button does." This is our primary CTA.
03 · Request
Send judgment to the repository without editing the file behind its back.
Once a repository adopts an intent, intent.md owns the product decision. A PM, designer, or researcher proposes a structured amendment in Pathmode; the repository agent receives the field, proposed value, and reason against one exact base revision.
- No Git required for judgment: Request a replacement, addition, or removal from the hosted intent without asking a product teammate to operate the coding agent.
- Exact-base request: Every request names the repository revision it was written against. If the file moves first, the stale request cannot silently overwrite newer judgment.
- Repository agent applies it: The operator's agent reads and deliberately applies the request to
intent.md. Pathmode records consumption, but never rewrites the repo-owned body from the browser.
$ list_intent_change_requests
1 open · base 22a04263b2e1…
$ get_intent_change_request
replace outcome · observable in fewer than 3 steps
$ intent_save
applied · revision 6b76ea2687d4…
authorization pending · stop before implementation
04 · Authorize
Authorize the revision your implementation agent will use.
The repository agent applies the request to intent.md and syncs the result. Pathmode derives the diff from immutable revisions. A human reviews that change and authorizes the whole proposal at that exact revision. Pathmode records who authorized it and when; this is separate from keeping individual draft suggestions.
- Repository-owned: The product decision lives beside the code it governs. Hosted edits become requests; they do not silently overwrite the canonical file.
- Revision-bound gate: A material change produces a new revision and clears the prior verdict. Until a signed-in human authorizes the new revision, the agent is told not to implement.
- One role, one next action: Judgment owners review the server-derived diff in Pathmode. Repository operators consume requests from Claude Code, Cursor, Codex, or any connected MCP client.
- Private evidence stays private: The repo receives the decision and safe references. Customer material and the reasoning behind it stay in the connected workspace.
- Start repo-local: Choose the coding agent that should read and preflight
intent.md:/plugin marketplace add pathmodeio/claude-plugin /plugin install pathmode@pathmodeInstalls the Pathmode plugin and MCP server for Claude Code.
Then run
/preflightin the repository you're about to change.
05 · Verify
Check the implementation. Then measure the outcome.
With GitHub connected and the pull request linked to an intent, Pathmode checks the merged diff against the spec. That review assesses the implementation; outcome measurements tell you whether the change helped customers.
- Findings write back:When a build contradicts the spec, the agent records a finding, what the spec assumed versus what the build revealed. It rides into the next agent's prompt and can flip a verification check to failing, so the spec converges instead of repeating a dead premise.
- Outcome verification: Define observable outcomes in the intent, then record measurements after shipping. A passing code review alone does not establish that the customer problem improved.
- Discovery compounds:Each shipped feature changes how users behave. Feed what you observe back in as the next cycle's evidence: discovery and delivery feed each other, release after release.
Why verification needs a human gate: The Missing Gate in the Software Factory →
Outcomes measured and on the record, ready for the next cycle
Don’t take our word for it
Still not sure Pathmode fits? Ask an AI you already trust.
Click a button and your AI of choice opens with the question pre-filled — what Pathmode does, who it’s for, and whether it’s right for your team. Answered in its words, sources and all. Not ours.
Opens a new tab in your chosen AI with the question ready to send.
Put product judgment where the agent works.
Start with a free intent.md in your repository. Connect Pathmode when your team needs private evidence, structured change requests, and exact-revision authorization.
No account or API key required for the repo-local workflow.