lockstep-team-agent/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
Lockstep is free and open source. If it helps your team keep decisions straight, star the repo on GitHub so other teams can find it.
---
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.
-->
How it compares
| | Nothing | Slack / docs | CODEOWNERS | **Lockstep** |
| --------------------------------------------------- | :-----: | :----------: | :--------: | :---------------------------: |
| Agents learn what other agents decided | ❌ | Manual | ❌ | ✅ Automatic |
| Decisions ranked by blast radius | ❌ | ❌ | ❌ | ✅ Usage graph |
| Changes routed to the services that consume them | ❌ | ❌ | ❌ | ✅ Dependency graph |
| "Does anyone use this endpoint?" answered instantly | ❌ | Manual | Partial | ✅ From the graph |
| Claude Code session continuity | — | Manual | — | ✅ Briefings + decision packs |
How It Works
Start with your own next session:
A **decision** is a durable rule or architectural choice that shapes future work. A **change** is a routine event — captured, but only surfaced when it matters. A PM can establish the same continuity by reviewing requirements from a brief before any code is connected.
As teammates join
The same ledger grows into coordination across developers and repos. For example, a route change in one service can reach the developers whose services consume it:
1. **Capture** — A coding-agent hook diffs the working tree and publishes _changes_ with a canonical surface ID (http:POST /session, proto:auth.v1.Auth/Login). When an agent makes a real decision, it logs it with propose_decision.
2. **Rank** — Each decision and change gets an **impact** score = how many services consume the affected surface (its blast radius). This is what keeps signal high and noise quiet.
3. **Route** — Changes fan out to exactly the repos that declared a dependency on the changed surface (lockstep.yaml). The agent can also ask consumers("http:GET /orders/:id") — _"does anyone use this?"_ — and get an answer from the graph instead of pinging a human.
4. **Replay** — On session start, each agent receives a briefing of what changed and what's binding since it was last here, **highest blast radius first** — so it's aware before it acts.
5. **Bind** — Cross-cutting decisions (high impact) stay open until an affected team acknowledges them; own-area decisions bind on assertion. A PR-time gate fails any contract change with no binding decision.
Quick Start
Choose your starting point: developer or product manager. Both use the full dashboard and the same project history.
> **Pilot release status:** CLI **0.3.0** is published on npm and listed in the MCP registry, alongside the matching API and dashboard changes in this repository. Hosted rollout and a real authenticated Claude-session verification are still pending, so the hosted links may run an earlier release. Complete those checks before inviting pilot participants.