Writing a PRD
A PRD (Product Requirements Document) is the starting point of every task flow in Task Master. It defines what you’re building and why. A clear PRD dramatically improves the quality of your tasks, your model outputs, and your final product — so it’s worth taking the time to get it right.You don’t need to define your whole app up front. You can write a focused PRD just for the next feature or module you’re working on.
You can start with an empty project or you can start with a feature PRD on an existing project.
You can add and parse multiple PRDs per project using the —append flag
What Makes a Good PRD?
- Clear objective — what’s the outcome or feature?
- Context — what’s already in place or assumed?
- Constraints — what limits or requirements need to be respected?
- Reasoning — why are you building it this way?
Writing a PRD for Task Master
An example PRD can be found in .taskmaster/templates/example_prd.txt
- Chat about requirements — explain what you want to build.
- Show an example PRD — share the example PRD so the model understands the expected format. The example uses formatting that work well with Task Master’s code. Following the example will yield better results.
- Iterate and refine — work with the model to shape the draft into a clear and well-structured PRD.
Where to Save Your PRD
Place your PRD file in the.taskmaster/docs
folder in your project.
- You can have multiple PRDs per project.
- Name your PRDs clearly so they’re easy to reference later.
- Examples:
dashboard_redesign.txt
,user_onboarding.txt
- Examples:
Parse your PRD into Tasks
This is where the Task Master magic begins. In Cursor’s AI chat, instruct the agent to generate tasks from your PRD:- Parse your PRD document
- Generate a structured
tasks.json
file with tasks, dependencies, priorities, and test strategies