The thinking behind every request.
PRDs, specs, research and decisions — written in Markdown, versioned on every save, and attached to the posts that prompted them. Internal, always: your customers never see them.
So the public post can stay simple.
A feature request is one sentence from a customer. The work behind it is a spec, a rejected approach, a decision someone will ask about in six months. Put all of that on the board and the board becomes unreadable.
So it lives in a document instead — attached to the post, readable by your team, invisible to everyone else. The post keeps its votes and gets one answer at the end. No sub-items, no threads of half-decisions.
Eight types out of the box. Then whatever you call yours.
A type is the question the document answers. Every workspace starts with these eight; rename them, recolour them, reorder them, or add the ones your team actually uses.
Every save kept. Every change visible.
Six months later, the useful question isn't what the spec says. It's what it used to say, and who changed it. Open any version and the answer is highlighted in place.
- Every save, a full snapshot
Not a delta. Version 1 is written the moment the document is created, so the history is complete from birth.
- Diffed block by block
Paragraphs, list items and code blocks are compared whole, then word by word inside any block that was rewritten.
- Restore adds, never overwrites
Restoring an old version re-applies its content as a new version on top. Nothing in the chain is destroyed or rewound.
- No pruning, no noise
Versions accumulate — there's no retention window. Save a document you didn't actually change and nothing is written at all.
Twelve tools. No ceremony.
Your roadmap,
on autopilot.
Free for 30 days. No card, no sales call. Cancel anytime.