Philosophy
Why a product description drifts, and the rules unbranch holds so yours does not. Read the principles →
Know what was agreed.
unbranch keeps your product’s description and the decisions behind it in one record that your team and your agents read. These docs explain the ideas behind it, how to use it, how to connect an agent, and how to use it well.
ProposeConsentCommitModel
Nothing enters or leaves your product model except through that loop. A proposal is written down. Every member of the project answers it. Acceptance becomes a commitment to deliver, and verified delivery is what the model records as real.
Using unbranch
Import your product, write proposals, give consent, and deliver what was agreed. Start with an import →
Connect an agent
Claude, Claude Code with @unbranch/kit, Cursor, VS Code and any other MCP client.
Connect one →
Best practices
What to send, how to review a draft, and how to object so the next revision fixes it. Do it well →
Set up a repository in one commandnpx @unbranch/kit init — connects the repository and its coding agent to your team’s agreed model.