Dupflo

Decision Ledger — Development skill for Claude Code

Development community

Three Claude Code agent skills that record which structural decisions you could actually defend, and give it back as a map of your project.

How to install Decision Ledger

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Dupflo/decision-ledger and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Decision Ledger does

Three Claude Code agent skills that record which structural decisions you could actually defend, and give it back as a map of your project.

Alternatives in Development

ADR Rubber Duck — ADR（Architecture Decision Record）の壁打ち相手としてヒアリングを通じて意思決定を整理し、ADRドラフトを作成する 974 ★
Obsidian ADR — Generate a decision record when the vault structure changes — the vault knows why it knows what it does 277 ★
Compass — Compass — Record a Decision 262 ★

README

Decision Ledger

*Three agent skills for Claude Code: `/ledger`, `/ledger-audit`, `/ledger-report`.*

**Two developers ship the same feature this week. In three weeks, only one of them can still explain it.**

![Two panels, same desk, same green diff, same stack of merged and approved pull requests. Left, labelled VIBECODER: asked "Why a server only cookie?", the developer freezes, and his thought bubble holds a server rack, a plate of actual cookies, and a question mark. Right, labelled AGENTIC DEV: same question, and a flowchart in the thought bubble. REQUEST, then NEEDS STATE? Yes leads to SESSION TOKEN, no leads to SERVER ONLY COOKIE. Both branches are ticked: the answer depends on the condition.](assets/vibecoder-vs-agentic-dev.png)

Nothing in the diff tells you which one you are. Decision Ledger is three agent skills for Claude Code that keep the record: at each structural decision they ask you to take a position, note whether you could hold it, and hand it back as a map of your project. You shipped twelve thousand lines this quarter. How many of those decisions could you defend in review?

**Status: early.** This is an experiment, not a product. There is no usage data yet. I'm running it on my own projects first and will publish what I find, including if the answer is that nobody tolerates the friction.

The three skills

They install as normal Claude Code skills, in `~/.claude/skills`. One promise each, and only the first one loads on its own. The other two you invoke by name, like any slash command.

Skill	When
`/ledger`	At a structural decision. Asks once, records, writes the code regardless. The only skill with a broad description, because interception has to fire without being asked for.
`/ledger-audit`	Once per project, on a codebase that predates the ledger. The one moment a batch of questions is welcome, because you sat down for it.
`/ledger-report`	At a commit or a pull request. The map, and nothing appended to