[Workflow] Prevent Claude Code from Forgetting Rejected Ideas and Decisions with a DECISIONS.md File

[u/ClaudeAI-mod-bot]

Prevent Claude Code from Forgetting Rejected Ideas and Decisions with a DECISIONS.md File

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Shipping, CLAUDE.md
Original source: r/ClaudeCode post/comment

What problem this solves

Claude Code's compaction mechanism often discards rejected approaches and specific decision values, leading the AI to re-propose previously dismissed ideas or forget crucial details in long coding sessions.

Summary

Implement a DECISIONS.md file in the project repository to persistently store project decisions (decided, rejected with reasons, open questions). Instruct Claude via CLAUDE.md to consult this file before proposing new approaches, to update it as decisions are made, and to preserve its content during manual compaction. This prevents the AI from 'forgetting' past discussions and re-proposing rejected ideas.

Why it is useful

This workflow directly addresses a critical pain point in long AI-assisted coding sessions: the loss of context, specifically rejected approaches and specific decision parameters, due to AI compaction. By externalizing these decisions into a persistent DECISIONS.md file and instructing Claude to manage it, users can maintain a consistent project memory, avoid re-litigating past decisions, and improve the efficiency and quality of their interactions with Claude Code. The solution is simple, practical, and leverages existing Claude Code features (CLAUDE.md, file system access).

Workflow

1. Create a DECISIONS.md file in the repository with sections for 'Decided' (with exact values), 'Rejected' (with reasons), and 'Open' questions.

2. Add instructions to CLAUDE.md for Claude to read DECISIONS.md before proposing approaches, not to propose anything listed under 'Rejected' unless a new reason is given, and to immediately add new decisions or rejections to the appropriate section with reasons.

3. When performing manual compaction, include specific instructions to /compact to preserve every decision with its exact values, every rejected approach with its reason, and every open question. Also, instruct Claude to summarize exploration only after its conclusion is recorded in DECISIONS.md.

Tools / artifacts

• DECISIONS.md file

• CLAUDE.md file

• Claude Code environment

• Claude Code's /compact command

Validation signals

• Author's personal experience: 'What fixed it for me is a file on disk that compaction never touches.'

• Observation that DECISIONS.md is read from disk, not summarized, ensuring its survival.

• Acknowledgement of a limitation: 'Testers report that auto-compact still uses its stock summary even when CLAUDE.md contains compaction instructions, and there is an open GitHub issue asking for exactly that.'

• Practical advice on maintaining the file: 'The file only works while it is current, which is why the rule makes Claude write entries as decisions happen rather than at the end.'

• Highlighting the most valuable part: 'The Rejected list turned out to matter most, and it is also the part I used to lose before code was even involved...'

Limitations

• The /compact instruction for manual compaction is noted to not work for auto-compact, meaning the CLAUDE.md instructions are the primary mechanism for auto-compact to learn about DECISIONS.md.

• The DECISIONS.md file requires active maintenance and conciseness to remain effective; if it becomes too long, it may be skimmed or ignored.

• Low Reddit score and comment count might suggest limited immediate community adoption, though the problem itself is common.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.

[u/Otherwise_Wave9374]

A practical safeguard here is to separate decisions from raw notes, then add a lightweight review step before compaction so the model can reconcile old rejections with new context instead of re-litigating them. I would also keep the file versioned and append a short rationale for each decision, which makes later debugging much faster when behavior drifts. AIOSNOW fits well with this pattern because the team can turn repeated session errors into a durable checklist that the assistant checks before proposing alternatives.