Find the product decisions a request leaves open, before your coding agent builds.
The repo gets the decision. Pathmode keeps the evidence and judgment behind it. A change's
reason lives in an intent.md your repository owns, in the open IntentSpec
format, and a deterministic preflight tells you and your agent whether it is ready to build from.
No account needed.
| You want to | Start with |
|---|---|
Check an existing intent.md or OpenSpec change |
npx -y @pathmode/cli preflight (CLI on npm) |
| Have Claude Code draft and preflight specs with you | claude-plugin |
| Use another MCP client, such as Cursor, Codex, or Claude Desktop | mcp-server |
Put intent.md in front of an OpenSpec proposal |
pathmode-intent |
Validate intent.md in CI |
validate-intentspec-action |
| Implement the format, or propose a change to it | intentspec |
| Call the REST API directly | pathmode.io/developers |
| See it work on realistic code | fieldnote and one recorded run |
/preflight is what you type in Claude Code's chat. check_intent_readiness is the MCP tool your
agent calls on its own. npx @pathmode/cli preflight runs in a terminal or in CI. All three grade
with the same code and return the same verdict. A pass means the spec is complete enough to build
from, not that the decision is right, and an open product choice blocks it until a person decides.
IntentSpec open product-intent format
└── intent.md the file your repository owns
├── Pathmode evidence, attributed review, staleness across repositories
└── pathmode-intent adapter into OpenSpec
intent.md -> proposal -> specs -> design -> tasks
Without an API key nothing leaves your machine: the CLI's preflight and validate, and the MCP
server in keyless mode, make no network request. What a connected workspace receives is in the
privacy policy.
