Roadmap 'no's that stay no
Product and designProduct team deciding what not to build
In September we decided not to build a Slack bot this quarter: three requests, all from free users. In October an engineer asked Claude Code to 'scope a Slack integration' and it spent 30k tokens on a plan before anyone noticed.
How do I stop AI agents scoping features our product team already decided not to build?
Record each roadmap call, yes or no, in ArcRoom with arcroom decide and the reason. When a prompt touches that topic, recall brings the decision, like 'no Slack bot in Q4' and why. When the call changes, report the old one with arcroom wrong and save the new one. Recall is a reminder: if an engineer still wants to build it, nothing stops them.
Also asked as: An engineer's agent spent ages planning a feature we already said no to. How do I prevent that? · How do I tell AI agents what is not on the roadmap? · Can Claude Code know about product decisions made last month?
Roadmap calls, yes and no, are saved with arcroom decide and the reason.
- Decision
- Recall
- Wrong-memory report
Recall: Decision (pm-lena, Sep 18): no Slack bot in Q4
Step by step
- Roadmap calls, yes and no, are saved with arcroom decide and the reason.
- When a prompt touches the topic, recall brings the decision.
- When the decision changes, the PM reports the old one with arcroom wrong and saves the new one.
What the agent sees
Recall: Decision (pm-lena, Sep 18): no Slack bot in Q4
why: 3 requests, all free tier; revisit in JanuaryCompared with today's tools
Roadmap tool (Linear, Productboard) notes
Mark the request 'won't do' with a comment on the roadmap item.
- Setup
- None
- Ongoing
- Low, but engineers' agents never see it
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
Zep's 'true until' facts fit a 'no until January' decision well, but you'd need an app to ingest it; ArcRoom surfaces it inside the engineer's Claude Code when the Slack prompt is typed.
Where it stops
Recall is a reminder. If the engineer still wants to build it, nothing stops them; rules agents can't bypass are on the roadmap.
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
- A PRD written over two weeks, decisions keptProduct manager writing PRDs in the repo's docs folder with Claude Code
- Usability findings tied to the screen they're aboutProduct designer and researcher running usability tests
- Design-system rules Cursor actually followsDesign engineer and frontend team using Cursor and Claude Code