Build
Features, stories, documents, the Build Pack, the product map, Plan, Launch and Results.
Features, stories and documents
- A feature's pageEvery feature has one page in Build › Features, at /p/{product}/build/features/{KEY}. It goes from why the feature exists, to a spec that's ready to build…
- Features and Stories listsBuild › Features lists every feature on your roadmap; Build › Stories every story and bug. Both read the same data as before; only the pages are new.
- Files on features and storiesA feature's files are under Files in its Properties, on the right of its page in Build › Features. A story or bug has its own Files: in its drawer…
- DocumentsBuild › Documents lists every document of the product: PRDs, help articles, briefs, prototype prompts, launch plans and the rest.
- The spec interviewA feature without a spec can start from seven plain questions instead of a blank PRD. Open the feature in Build › Features and choose Start the spec…
- Compare, and decide between optionsCompare two segments (Learn › Questions › Compare): who to build for first, row by row from what each segment's people did, never one total score.
The Build Pack and the map
- Build PackA Build Pack is everything a coding agent needs to build one feature, in one place. It leads with why the feature matters and the customer evidence behind…
- Product mapThe product map tells MindBacklog what your product does for its users and how it's built: its parts (apps, services, modules, data, external services, APIs)…
- Publish checkBuild › Publish check helps you check that you haven't made something public by accident. It lists only what changed since you last marked a publish.
Plan, launch and results
- Initiatives and the timelineAn initiative is the why above your features: a problem worth solving, how much time it is worth, and what you expect it to change.
- PlanBuild › Plan lists the foundations your product needs before launch, the ones that are expensive to add later: sign-in that can be recovered safely…
- Launch and Tell the N who askedWhen something ships, two things are worth doing: tell the people who asked for it, and tell everyone else. MindBacklog drafts both.
- ResultsBuild › Results checks what you predicted against what happened. It answers one question per initiative: did it work? Every number on the page comes from a…
Import and export
- Import features from a CSVAlready keep a list of features in Jira, Productboard or a spreadsheet? Bring it into MindBacklog in one go from Build › Features › More (⋯) › Import a CSV.
- PDF, Word, PowerPoint and MarkdownEvery document exports from its page in Build › Documents (the Export menu), from its row in the Documents list (the download button: PDF, Word)…
- Importing and exporting your dataNot available: exports to Google Docs, Google Slides, Notion, Excel or Keynote. In every CSV, a cell a spreadsheet would run as a formula is written as…
Names that changed
- Feature detail pages are now a feature's page in BuildA feature's detail page is now its page in Build › Features, at /p/{product}/build/features/{KEY}; old /items/{KEY} links open it.
- The Tracker is now Build › StoriesThe Tracker is now Build › Stories: every story and bug of the product in one list, whatever the old tracker setting was.
- The Roadmap is now Build › Features, the board and the initiatives timelineThe Roadmap's pages are now in Build, and old Roadmap links open their new place: Statuses keep their meaning with new words…
If you can't find it here, write to [email protected] and say which screen you were on.