For engineers
AI starts implementing without guessing, and you stop updating boards.
Requests, acceptance criteria, tasks, pull requests and progress arrive connected, so Claude Code and Codex do not burn time hunting for specs and guessing.
What hurts an AI coding agent is not only a lack of information. It is that the relationships — which request a task came from, what done means, what it affects — are not machine readable. PM on Rails connects request to story to acceptance criteria to task to pull request to progress in a graph, and hands that delivery map to your agents.
Read the same information from Claude Code and Codex
MCP puts requests, tasks and acceptance criteria within reach while you build.
Never lose the link between task and pull request
Link the task on the board to its pull request and send completion back into progress.
What developers lose in AI coding
Spec hunting before implementation
The agent burns time working out where to write and what to satisfy, reading unrelated files and polluting its own context.
AI writes in the wrong place
When it cannot read which module or task owns what, the agent picks a location by guesswork.
Acceptance criteria are vague
A task title alone does not say what counts as done, so it comes back in testing or review.
Impact of changes goes unnoticed
When a request or scenario changes, nobody notices how it hits work already in progress.
Board updates pile up
Implementation moves forward while the task and its parent story stay untouched.
New joiners cannot see the whole
The relationships between requests, specs, scenarios, tasks and pull requests exist only in someone's head, so neither people nor AI can pick them up.
PM on Rails does not hand your agents a guessing game
What to build comes from acceptance criteria, the relationships come from the graph, and both reach your agent over MCP.
Read the background, not just the task
Ask for the background and acceptance criteria of a task and the answer walks the chain from request to story to acceptance criteria to task. The agent can read why it is being built and what done means before touching code.
- Trace the background of a request
- Read the acceptance criteria
- Search similar requests and past decisions
Less exploring, less guessing
PM on Rails holds the relationships between requests, acceptance criteria, tasks and pull requests as a graph. You can hand over the relevant context and its connections instead of making the agent read half the repository.
- Walk relationships to gather the needed context
- See the blast radius before implementing
Pull requests flow back into tasks and progress
When work starts, the response includes a branch name and a one-line trailer for the pull request. Open the pull request with those and the task links itself, with merging completing it automatically.
- Start work, get the branch name and trailer
- Merge completes the task and recalculates the parent story
Notice spec changes made after you started
If an upstream request or acceptance criterion changes mid-implementation, the agent can detect that upstream moved after work started, instead of finishing against a stale spec.
More on tracking changesCreate, update and batch it all from the conversation
Creating and updating requests, stories, acceptance criteria and tasks, handling bugs and proposing estimates all happen in conversation. Management moves inside the implementation flow instead of pulling you back to a screen.
- Read, create, change, assign and complete
- Atomic batch execution supported
Connecting (setup)
Issue a token and register the MCP connection with your agent. That is it.
- 1
Issue a token
Create an access token under Integrations → Tokens.
- 2
Register the MCP connection
Run npx pm-on-rails in your terminal (it calls claude mcp add for you).
- 3
Other agents work too
Codex, Cursor and any MCP-capable agent connect with the endpoint and a token.
Give Claude Code and Codex a map they can implement from.
Requests, acceptance criteria, tasks and pull requests arrive connected, so your agents stop dissolving time into exploration and guesswork.
Guides for other roles