Organize a spec and shape the work that follows
Write your planning docs and connect them to work the team can start right away.
Write the PRD
Open the Planning tab
Select Planning in the project sidebar and the PRD, Feature spec, and User flow tabs appear. Tabple remembers the tab you opened last on this device, and the address carries it too, so the same tab opens straight away. In a project that has neither a PRD nor a feature spec yet, a screen for choosing how to start opens first.
Write the PRD yourself
The PRD tab has five sections: Overview, Core value, Target & scenarios, Success metrics, and Attributes. One-line summary, Product goals, Background, User problem, Solution, and Differentiators vs. competitors are written as text; Key target users, Usage scenarios, Key KPIs, and Expected risks are filled in by adding entries; Product category, User roles, and Service environments are set as attributes. Click a field to edit it right away, drag over text to bring up the formatting tools (bold, italic, strikethrough, list, text color, highlight, and emoji), and your changes are saved automatically a moment later.
Draft it from questions
On a plan that can use AI, opening the Planning tab of a project with no PRD and no feature spec shows the start screen, with Start with a questionnaire and Extract from your own material. The questionnaire asks six questions one at a time (the first three are required) and your answers become a PRD draft; if you have meeting notes or a planning memo, paste them into Extract from your own material (30 characters or more) and a PRD draft and a feature spec draft are created together.
Polish the wording
There are two ways to polish the PRD. In Product goals, Background, User problem, Solution, and Differentiators vs. competitors, drag over some text and click Ask AI to revise in the formatting tools: you get a revised version of just that part, which you approve or reject. AI-optimize all, below the contents on a large screen, tidies all six fields — including the one-line summary — in one go, and because it overwrites the current content a confirmation comes first.
Build the feature spec
Start with requirements
A feature spec has three levels: requirement, feature, and sub-feature. Build it by hand with Add requirement at the top right, and switch how you see it between Tree view and Directory view. If you can use AI, Generate from PRD in the AI menu builds the structure from the PRD in one go (the PRD must exist first, and if items already exist they are all deleted and rebuilt, so a confirmation comes first). In the same menu, AI improve all strengthens the description and acceptance criteria of every item, and AI add items suggests missing requirements and features.
Edit the details
Click an item and the Feature detail panel lets you change its title, status (Not started, In progress, Done, Blocked), priority (Low, Medium, High), points, tags, description, and acceptance criteria. You can check off each acceptance criterion, leave comments on an item, and see every comment in the project, filtered by resolved or not, under All comments in the header. Drag items to reorder them, duplicate them, or move them to another requirement.
Export to tasks
Send the finished feature spec to the board in one pass with Export to tasks. Pick the items (up to 200 at a time) and the target column, choose whether to include feature descriptions and whether to create acceptance criteria as subtasks, and the tasks are created. Each task title starts with a bracketed tag for its level, the item's priority carries over to the task, and every task you create shows up under Linked tasks in the item's detail.
Review the user flow
Open the User flow tab
The User flow tab shows the order in which users move through your features. Flows are listed on the left, and your changes are saved automatically. With read-only access (Viewer) you can only look.
Generate a flow
Create a new flow by hand with Build manually, or use Auto-generate with AI if you can use it. AI generation needs at least one feature in the feature spec, lets you describe the flow to emphasize, and takes the PRD into account when there is one. The generated flow is laid out neatly for you.
Edit steps
⌘+ZDouble-click a step (node) to open a window where you change its name, description, and type (Section, Page, or Action) or delete it. Use Add node at the top right to attach a new step after the selected one (or after the last one if nothing is selected), double-click a connector to delete it, and if you slip, press ⌘Z to undo and ⌘Y to redo.
Make a revision
Revision in the header copies the current flow into a new version (Create a revision). Leave the original as it is and try another layout, then switch between versions in Version history on the right, and delete a version from the list on the left.
Sharing and exporting
Read-only share link
Choose Share at the top of the screen, pick an expiry (7 days, 30 days, or Never), and click Create a share link. Anyone with the link can read the PRD and the feature spec without logging in, but the user flow is not included. In the popup you can copy the link, check its views and expiry date, and block it at once with Disable link.
Export to Markdown
Under Export, choose Full planning document (the PRD and the feature spec in a single file), PRD only, or Feature spec only, and a Markdown (.md) file is downloaded. The user flow is not part of the export.