Built as working context, not shelfware.
This resource is meant to be useful inside the tools where product work now happens: your codebase, your notes, and your AI-assisted workflow.
01
Paste the markdown into Claude, ChatGPT, Cursor, Codex, Gemini, or another AI agent as reusable project context.
02
Use it before a planning, implementation, review, or audit session so the agent has constraints, criteria, and working structure up front.
03
Adapt the sections to your product, team, or repo before asking the agent to execute against it.
Markdown previewroadmap-prioritization-canvas.md
# Roadmap Prioritization Canvas Use this to compare build, buy, defer, and remove decisions with the same language. ## 1. Decision Frame ```md Decision: Owner: Date: Product surface: User affected: Current workaround: Decision deadline: ``` ## 2. Options | Option | User value | Cost | Risk | Reversibility | Learning value | Notes | | --- | --- | --- | --- | --- | --- | --- | | Build | | | | | | | | Buy | | | | | | | | Integrate | | | | | | | | Defer | | | | | | | | Remove | | | | | | | ## 3. Scoring Score 1-5: - User pain: how painful is the current state? - Frequency: how often does it happen? - Strategic fit: does it move the product direction? - Implementation confidence: can we ship it cleanly? - Operating cost: will this create ongoing support? - Reversibility: can we change our mind later? ## 4. Recommendation ```md Recommended path: Why: What we are not doing: Smallest useful version: Validation signal: Review date: ``` ## 5. Roadmap Hygiene - [ ] The decision can be explained without internal jargon. - [ ] The tradeoff is explicit. - [ ] The next action is owned. - [ ] The team knows what would change the decision. - [ ] Deferred work has a revisit trigger, not vague someday status.