A PRD (Product Requirements Document) is the starting point of every task flow in Taskmaster. 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
The more context you give the model, the better the breakdown and results.
An example PRD can be found in .taskmaster/templates/example_prd.txt
You can co-write your PRD with an LLM model using the following workflow:
This approach works great in Cursor, or anywhere you use a chat-based LLM.
Place your PRD file in the .taskmaster/docs folder in your project.
dashboard_redesign.txt, user_onboarding.txtThis is where the Taskmaster magic begins.
In Cursor's AI chat, instruct the agent to generate tasks from your PRD:
Please use the task-master parse-prd command to generate tasks from my PRD. The PRD is located at .taskmaster/docs/<prd-name>.txt.
The agent will execute the following command which you can alternatively paste into the CLI:
task-master parse-prd --input .taskmaster/docs/<prd-name>.txt
This will:
tasks.json file with tasks, dependencies, priorities, and test strategiesNow that you have written and parsed a PRD, you are ready to start setting up your tasks.