A PRD written over two weeks, decisions kept

Product and designProduct manager writing PRDs in the repo's docs folder with Claude Code

I wrote the bulk-export PRD over nine sessions. By session six the agent had forgotten that we'd ruled out offline mode for v1, and it wrote a section on offline sync. Meanwhile an engineer's Codex had started scoping offline too.

How do I stop Claude Code forgetting decisions I made earlier while writing a long PRD?

Record each PRD decision in ArcRoom with arcroom decide and the reason after --why. Recall then puts the PRD's decisions in front of every prompt, yours and the engineers' Codex too. The last-run note tells each new session which sections are done and which are open. ArcRoom stores the decisions, not the PRD, which stays in your docs folder or Notion.

Also asked as: My AI agent wrote a section on something we already ruled out. How do I stop that? · How do I keep product decisions consistent across many AI writing sessions? · Can an engineer's Codex see the decisions in my PRD?

The work

Each choice is saved with arcroom decide and the reason.

ArcRoom keeps
  • Last-run note
  • Split into parts
  • Decision
  • Recall
The next agent gets

$ arcroom decide "No offline mode in v1" --why "2 of 14 interviews asked; sync conflicts add 3 weeks"

Step by step

  1. Each choice is saved with arcroom decide and the reason.
  2. The last-run note tells each new session which sections were done and which were open.
  3. Recall puts the PRD's decisions in front of every prompt, mine and the engineers'.
  4. Open questions are tracked as parts with split_task.

What the agent sees

$ arcroom decide "No offline mode in v1" --why "2 of 14 interviews asked; sync conflicts add 3 weeks"
Recall (engineer's Codex, next day): Decision (pm-lena, Oct 28): no offline mode in v1

Compared with today's tools

Notion PRD with a decisions table

Keep a decisions table at the top of the PRD and paste it into agents when needed.

Setup
30 min
Ongoing
Paste the table into each session, ~3 min; engineers rarely do

ArcRoom

Every agent reads the team playbook before it works and writes to it when it finishes. Nothing to update by hand.

Setup
2 min (npx arcroom init)
Ongoing
None

Mem0 extracts facts from chat but doesn't record who decided what with the why, and it only reaches the engineer's Codex if that agent searches; ArcRoom recall puts 'no offline in v1' in front of it unasked.

Where it stops

ArcRoom stores the decisions, not the PRD. The document still lives in your docs folder or Notion.

Try it in your project

Works with the agents your team already uses, and any agent over MCP or the HTTP API.

More in product and design