Lockstep AI MCP server

Lockstep

Keep decisions consistent. Turn product briefs into clear implementation context.

Start with one developer or one product manager. Grow into a shared decision record for your team.

Website · ▶ Try it live · Quick start · For product managers · How it works · Deploy

Yesterday, you and Claude renamed POST /login to POST /session. Today, a fresh session writes a client against the old route. The decision was made; the next session never received it.

Lockstep gives developers and product managers two ways to start independently:

• Developers: keep accepted decisions across Claude Code sessions and check whether changed code may contradict them.
• Product managers: turn a product brief into reviewed requirements, track revisions, and copy a useful implementation brief before a developer joins.
• Teams: share the same ledger, route interface changes to affected services, and retain existing integrations, permissions, and PR enforcement.

For example, accept “exports expire after 24 hours, except internal previews.” A later Claude session receives that decision without another explanation. A PM can trace the requirement to its source, revise it for review, and share its accepted version with a developer.

Start with one real repo or brief. Invite a colleague when there is useful context to share; company-wide onboarding is not required.

<!-- Once recorded, the 25s two-developer demo GIF (storyboard in docs/DEMO.md) can become the lead visual, moved above the problem statement: -->

npx lockstep-cli onboard

How it compares

How It Works

Start with your own next session:

Shortened. The full README is on GitHub.