From user friction
to shipped code.
Pathmode closes the loop between product discovery and engineering delivery. Hand the approved intent to the agents that write the code, and when their pull request opens, review its diff against the intent. After merge, a separate check records what landed.
The complete discovery-to-delivery loop
Every feature traces from user friction through existing code to shipped code, and back to verification.
Evidence
Support tickets, user quotes, analytics signals
Codebase Context
The agent can record relevant files and current behavior
Intent Spec
Structured spec with outcomes and edge cases
Coding Agent
Claude Code or Cursor reads the live spec over MCP
Pull request
The agent names the intent on the branch or PR
Review and ship
An advisory check runs before merge; a separate check records what merged
Evidence
Support tickets, user quotes, analytics signals
Codebase Context
The agent can record relevant files and current behavior
Intent Spec
Structured spec with outcomes and edge cases
Coding Agent
Claude Code or Cursor reads the live spec over MCP
Pull request
The agent names the intent on the branch or PR
Review and ship
An advisory check runs before merge; a separate check records what merged
The loop continues: shipped features generate new evidence for the next cycle.
Read: codebase context grounds the spec
The agent already working in your repository records what it found where the change lands: the files involved, how they behave today, what a change would risk. It reads the working tree, so it sees what you have not committed yet. The spec hardens against what exists rather than what someone remembers.
- Your agent does the reading, so uncommitted work counts too
- Narrow outcomes around existing behavior instead of guessing
- Catch the case where the thing being specified half exists already
- An agent cannot turn its own notes into the standard it is graded against: you decide whether they count
- No repository connection needed for this, and no clone
Relevant Areas
Current Behavior
When a referenced pull request merges, Pathmode grades the real diff against the spec and moves the intent to shipped. The MCP server already serves outcomes and edge cases to connected agents.
Verification Suggestions
Push: the spec reaches the agent writing the code
Pathmode does not file tickets. Your tracker already does that, and a ticket is a copy that goes stale the moment the spec changes. The approved intent goes where the code actually gets written: Claude Code, Cursor, and any MCP client read the live spec, its constraints, and your constitution before they touch a file.
- 35 tools over the Pathmode MCP server, no copy-paste and no stale duplicate
- get_current_intent returns the objective, outcomes and edge cases
- get_constitution applies your standing rules to every task
- verify_implementation checks the diff against the spec that asked for it
- Works in Claude Code, Cursor, and any MCP-capable client
Objective
Users abandon signup at email verification. Make delivery reliable and offer a fallback.
Outcomes
Edge Cases
Constitution
Never add a third-party dependency for something the platform already does.
The agent reads the spec at the moment it works. Nothing to re-sync when it changes.
Pull: the pull request reports back
Coding agents name the intent on the branch or in the pull request. While the diff can still change, Pathmode runs an advisory review against the linked intent. A person can accept, reject, or waive findings. After merge, a separate check compares the merged changes with the spec and records what landed. A merge moves the intent to shipped; neither diff check proves the outcome improved for customers.
These checks surface where code and intent agree or diverge. Whether the spec asked for the right thing remains your team's judgment.
Supported Reference Patterns
pathmode:<uuid>intent/<uuid>Resolves PAT-<uuid>Closes PAT-<uuid>Fixes PAT-<uuid>- Agents write the reference themselves, taught by the spec they were handed
- Advisory review runs on open and updated pull requests; a separate check runs after merge
- Every judgment cites the files it rests on, and failures open findings rather than a passing grade
- A merge still checks an intent an agent marked shipped early, so an eager status flip cannot hide the diff
- Read-only: the App never writes to your repository
Fix email verification flow
fix/email-verification → main
Implements email retry logic with SMS fallback.
Resolves PAT-abc12345-e5f6-7890-abcd-ef1234567890
Merged by @engineer · 2 commits · 4 files changed
Fix checkout email verification flow
Illustrative post-merge verdict
Context Sync: always fresh
For agents that read files rather than speak MCP, one workflow pulls your workspace context from the Pathmode API and commits it to the repo. Your coding tools see current intents, constitution rules, and product strategy without anyone maintaining the files by hand.
- Generates CLAUDE.md for Claude Code and AGENTS.md for the open standard
- Generates .cursorrules for Cursor
- Generates intent.md with the active intent spec
- Plain curl against /api/v1/export, no custom action to trust
- Commits changes directly to your default branch
Add to your repo as .github/workflows/pathmode-sync.yml
name: Sync Pathmode Context
on:
schedule:
- cron: '0 6 * * 1-5' # Every weekday at 6am UTC
workflow_dispatch: # Manual trigger
permissions:
contents: write
jobs:
sync:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Pull latest Pathmode context
env:
PATHMODE_API_KEY: ${{ secrets.PATHMODE_API_KEY }}
run: |
for fmt in claude-md agents-md cursorrules intent-md; do
curl -sfSL \
-H "Authorization: Bearer $PATHMODE_API_KEY" \
-OJ "https://pathmode.io/api/v1/export?format=$fmt"
done
- uses: stefanzweifel/git-auto-commit-action@v5
with:
commit_message: 'chore: sync Pathmode context files'
file_pattern: 'CLAUDE.md AGENTS.md .cursorrules intent.md'Syncs every weekday at 6am UTC. Trigger manually from the Actions tab anytime. Needs a Pathmode API key with read scope.
Install in 2 minutes
Three steps. No config files, no tokens to paste.
Install the GitHub App
Go to Settings → Integrations in your Pathmode workspace and click "Connect GitHub." Authorize the Pathmode GitHub App for your org or account.
Pick your repository
Choose the repo Pathmode may read. It requests only what it needs: repository contents, pull requests, and webhooks.
Ground your first spec
For a repo-owned intent, ask your coding agent to record codebase context in intent.md. Eligible paid workspaces can also use Analyze codebase for a connected repository.
The Pathmode GitHub App is read-only on your code: repository contents for optional hosted codebase analysis and pull requests for advisory and post-merge checks. It posts check results but never changes your source files.
Close the loop between
discovery and delivery.
Code is downstream of intent. GitHub keeps the spec honest before and after it ships.
No credit card required · Free for solo builders