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
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:
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.
This approach works great in Cursor, or anywhere you use a chat-based LLM.