New in Pathmode

Pathmode now sees your code

So it can keep your why honest as you build.

Janne LammiMay 20, 2026

An IntentSpec on the left, with an Implementation Context section showing relevant code areas, current behavior, and verification suggestions on the right.

Every PM has shipped a spec only to discover halfway through that the thing was already half-built — or that it conflicts with code three teams over. Pathmode now reads your code while you draft, so every spec starts from what already exists, not from what you guessed.

PM scoping a new outcome

See what already exists, before you draft.

You're scoping a Google Analytics integration — Flow Visibility, you've called it. You write the objective, list outcomes, draft an edge case. Then you click Analyze codebase. Pathmode comes back with eight relevant files already in the repo: an OAuth lifecycle in app/api/integrations/google-analytics/, an orchestration engine in lib/integrations/analytics/engine.ts, even a strategy doc in docs/. The spec doesn't get torn up — it gets *narrowed*. You ship a smaller, sharper intent. The engineer who picks it up starts from where the work already is.

Implementation Context's Relevant areas list for a Google Analytics integration spec, showing eight specific paths in the codebase — OAuth lifecycle, orchestration engine, integration card UI, and strategy docs. — Relevant areas, surfaced before the spec hardens.

Drift, coming soon

What happens when the code drifts from the spec?

Soon, Pathmode will tell you at PR time. When a pull request changes a surface area that an approved spec touched, Pathmode will flag the drift — is the spec still honored? Is an outcome silently no longer true? This is the natural next step from Implementation Context: spec-time grounding, then PR-time reconciliation.

A foreshadowing screenshot of a Drift Detection check on a pull request, showing the spec being reconciled against the changed code. — A glimpse of what comes next.

Code is downstream of intent. That hierarchy is permanent.

Code shows you what's there. Intent shows you what your team wanted. Those aren't the same thing.

Code is the most reliable record of which intents your team has already committed to — and that's exactly the job Implementation Context lets it do. Not as the source of truth, but as evidence the spec has to answer to.

The spec stays in charge. The code becomes accountable. That direction is the one that matters.

Try Implementation Context on your next spec.

Paid plans. Beta workspaces first; broader access rolling out as the prompt tightens.

Start with Pathmode

See what already exists, before you draft.

What happens when the code drifts from the spec?

Code is downstream of intent. That hierarchy is permanent.

Code shows you what's there. Intent shows you what your team wanted. Those aren't the same thing.

The spec stays in charge. The code becomes accountable. That direction is the one that matters.