The approved spec, inside Claude Code, Cursor, or Codex.
The Bridge serves your signed acceptance criteria over MCP, straight into the editor your team already uses. The agent reads the spec before writing code, checks its own story with the same engine CI runs, and can never edit an approved criterion. Git is the transport: no server, no account, works on a bare clone.
UPDATED · AUGUST 2026
Install (one command)
pip install linebreak-gate linebreak-gate mcp install --editor claude-code # or: cursor · codex
Where does the approved spec come from?
Anywhere your docs already live. Your PRD stays in Notion, Jira, or a doc; what travels is the contract: the short list of checkable acceptance criteria. Scaffold a draft, let any AI distill your existing docs into it, then a human approves it, on the record:
linebreak-gate spec new # fill the draft in: by hand, or ask your AI to distill your PRD linebreak-gate spec approve .linebreak/spec-draft.yml \ --approver "Ana Lopez <ana@example.com>"
Approval lands the bundle in .linebreak/spec/ and commits it. The Bridge serves exactly that; CI enforces exactly that. Documentation stays where it lives; the contract travels in git.
The six tools the agent gets
- list_stories: every approved story, with status
- get_story: criteria with statement + check type: context BEFORE code
- next_story: what to build next
- set_story_status: doing · review · done
- check_story: the same evaluation engine as CI, scoped to one story
- spec_status: approval + offline signature state
Sealed en route: nothing in the Bridge can write, edit, or invalidate an approved criterion; that happens in the governance surface, re-approved by a human.
