The why behind
every change.
Every code change leaves a diff. What it doesn't leave is a record of why. Decobrief captures that reasoning — at the only moment it exists — as a plain-language file committed alongside the code.
Knowledge decays faster than code.
A diff tells you what changed. It cannot tell you why.
Preserved forever
The diff. The commit. The ticket. Every byte of what changed is in version control and searchable indefinitely.
Evaporates immediately
The reasoning. The constraint that ruled out the obvious approach. The context that made this the right call. It lives only in the developer's head — and starts fading the moment they move on.
Three steps. Under 90 seconds.
Finish the change
Merge a PR, close a ticket, or wrap up a session with your AI agent. The work is done.
Agent drafts the record
The agent reads the diff and writes what changed, how it was done, and proposes a plain-English why — verified from the code.
You confirm in one sentence
Read the draft. Say yes, or correct it. That is the only required human step. The record is committed with status set to confirmed.
What the agent can know — and what only you can.
The record is only as trustworthy as this split is respected. The agent must never present an unconfirmed why as fact.
| Field | Who fills it | Confidence |
|---|---|---|
| What changed | Agent — from the diff | High |
| How it was done | Agent — from the diff | High |
| Technical result | Agent — from tests and CI | Medium |
| Why / what-for | Agent proposes → you confirm | Low until confirmed |
| Business result | You — from the work item | Human only |
One file. One confirmation. Long-term memory.
A resolution record is a single markdown file committed alongside the code — and never deleted.
Works with your agent
Compatible with Claude Code, Cursor, GitHub Copilot, Windsurf, and any other AI coding agent. No new tool to install — attach this README and the agent knows the format.
See the workflowOne human step
The agent proposes the why. You confirm or correct in one sentence — while the reasoning is still fresh. Low friction by design, because the only way this habit sticks is if it costs less than a minute per change.
Why this mattersPermanent, browsable log
Every confirmed record lives alongside your code, forever. New team members can trace any decision back to its origin without scheduling a meeting — even years later. Your institutional memory, finally written down in plain language instead of buried in git history.
View resolution logSee it in action
This project uses Decobrief on itself. Every meaningful change has a resolution record — drafted by the agent, confirmed in plain language by the engineer who made it.
Browse the resolution log →