--- title: "Product Spec & PRD Tool: tied to feedback | Sleekplan" canonical_url: "https://sleekplan.com/documents" last_updated: "2026-09-12T20:57:37.174Z" meta: description: "Write PRDs, specs and decisions next to the feedback that prompted them. Eight document types, a version on every save with block-level diffs, and 14 MCP tools." "og:description": "Write PRDs, specs and decisions next to the feedback that prompted them. Eight document types, a version on every save with block-level diffs, and 14 MCP tools." "og:title": "Product Spec & PRD Tool: tied to feedback | Sleekplan" --- # 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. [**Start free **](https://app.sleekplan.com/sign-up/) ![Sleekplan Documents admin view: a PRD showing its document type, version history and two linked feedback posts](https://sleekplan.com/_ipx/f_webp&s_3456x1942/images/documents-admin-hero.png) Why a document ## 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. Never public Public board 148votesAdd more filter and sorting optionsFB-7319 Planned 62votesFilter by Not-Completed / Not-ClosedFB-7402 Under review Linked both ways Internal — your team only PRDv4 Saved views for the feedback board The problem What we are building How it behaves Out of scope Rollout The decision Document types ## 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. Knowledge Base How does this work? PRD What are we building? Spec How exactly? Plan In what order? Research What did we learn? Decision Why this way? Summary What came out of it? Project What's in flight? Your own type Version history ## 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. ![A Sleekplan document diff: one list item reworded with the changed words highlighted, and a newly added list item highlighted in full](https://sleekplan.com/images/documents-version-diff.png) _Version 4 of a PRD — one bullet reworded, one added._ - 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. Capabilities ## Twelve tools. No ceremony. Markdown bodies Headings, lists, quotes and code blocks from a / menu. Stored as Markdown, not a proprietary blob. Eight types built in PRD, Spec, Plan, Research, Decision, Summary, Project, Knowledge Base. Custom types Add your own. Rename, recolour and reorder the built-in ones. A version on every save Full snapshot, from version 1 onward. Save an identical document and nothing is written. Block-level diffs See which blocks changed, word by word inside the ones that were rewritten. Restore, never overwrite A restore re-applies old content as a new version. Nothing in the chain is destroyed. Linked to feedback Many-to-many, from either side. One piece of thinking can inform several posts. Internal by default Documents never render on your public board, portal or widget. Draft, published, archived Three states, so half-formed thinking doesn't read as settled. Search and filters Find by title, then narrow by type or status. 14 MCP tools List, read, write, link, diff and restore — the whole module is agent-addressable. Sleek Mate drafts them It offers to save what it just worked out, and never writes a document unasked. Explore other modules [F Feedback Board Voting, comments, statuses](https://sleekplan.com/feedback) [R Roadmap Public or internal planning](https://sleekplan.com/roadmap) [C Changelog Release notes that delight](https://sleekplan.com/changelog) [C CSAT & NPS Pulse-check satisfaction & loyalty](https://sleekplan.com/csat-nps) [S Surveys In-app surveys with logic](https://sleekplan.com/surveys) Get started in 4 minutes ## **Your roadmap,**** on **autopilot**. ** Free for 30 days. No card, no sales call. Cancel anytime. [**Start free **](https://app.sleekplan.com/sign-up/) [**Book a 20-min demo **](https://sleekplan.com/contact/sales)