AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 16, 2026, 10:00 JST

Team splits reason fields on Claude Code project to label whose judgment is whose

Team splits reason fields on Claude Code project to label whose judgment is whose

3 Key Points

  1. What happened

    A five-person team running a Claude Code-based development setup split each decision record's reason into 推奨理由(AI) and 根拠(人), and added a /decide skill that has Claude declare a strong or flat confidence level.

  2. Why it matters

    In their first week, six decision records were logged and all six followed the AI's recommendation, with only one carrying a human-written reason — so readers can now see which choices were made with no reasoning behind them.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The team's own definition of intent debt has two halves: reasoning that can't be traced later, and AI's "intent-looking" output being preserved as if it were a human decision. The first half is old — when a veteran leaves, the reasons leave with them. What AI changed, in their account, is the volume: one person now makes far more decisions per day with AI than before. The second half is newer, and they tie it to Addy Osmani's "The Intent Debt," which warns that an AI will invent a confident-sounding reason, which is worse than admitting it doesn't know.

Their answer was structural rather than behavioral. The AI's reasoning is kept, because it has value as research, but it is not allowed into the human rationale field; when a person offers no reason, the record says so explicitly rather than leaving a blank. Enforcement comes from a PR template section that a human writes, checked by a CI script that only verifies the line exists — never that the words are human, because no machine can prove that.

Where the system is honest about its gaps is instructive. The /decide skill may simply not fire, in which case no DEC ID appears and CI cannot notice. When Claude was turned loose on 98 migrated files, the token stream outside comments matched exactly and type checks and lint were unchanged, yet review found three errors — including a comment rewritten to cite a reason that was never in the original, the very failure mode the project is trying to prevent.

FAQ
What does the /decide skill actually do?
It makes Claude Code survey existing code and specs, present options with a recommendation and a self-declared confidence level, ask the person why when confidence is flat, then write the decision record and leave only an ID in the code.
What happens to code comments under their rules?
Comments may only carry the local "why" (constraints, workarounds, non-obvious choices) up to three lines, a reference like `// DEC-012-03`, a spec pointer, or a TODO with an ID. Translated code, background paragraphs and change history are banned.
Did cleaning up their migrated code comments work?
Yes. On 98 migrated application files, comment lines fell from 1,433 to 433 and blocks of four or more lines dropped from 53 to 3, though two of the three survivors were usage notes for build scripts outside the rules.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleLinus Torvalds leans on Claude Code to improve Linux kernel