Tasks.json Task Fields
Tasks in Task Master follow a specific format designed to provide comprehensive information for both humans and AI assistants.
Task Fields in tasks.json
Tasks in tasks.json have the following structure:
Field | Description | Example |
---|---|---|
id | Unique identifier for the task. | 1 |
title | Brief, descriptive title. | "Initialize Repo" |
description | What the task involves. | "Create a new repository, set up initial structure." |
status | Current state. | "pending" , "done" , "deferred" |
dependencies | Prerequisite task IDs. ✅ Completed, ⏱️ Pending | [1, 2] |
priority | Task importance. | "high" , "medium" , "low" |
details | Implementation instructions. | "Use GitHub client ID/secret, handle callback..." |
testStrategy | How to verify success. | "Deploy and confirm 'Hello World' response." |
subtasks | Nested subtasks related to the main task. | [{"id": 1, "title": "Configure OAuth", ...}] |
Task File Format
Individual task files follow this format:
Features in Detail
Best Practices for AI-Driven Development
📝 Detailed PRD
The more detailed your PRD, the better the generated tasks will be.
👀 Review Tasks
After parsing the PRD, review the tasks to ensure they make sense and have appropriate dependencies.
📊 Analyze Complexity
Use the complexity analysis feature to identify which tasks should be broken down further.
⛓️ Follow Dependencies
Always respect task dependencies - the Cursor agent will help with this.
🔄 Update As You Go
If your implementation diverges from the plan, use the update command to keep future tasks aligned.
📦 Break Down Tasks
Use the expand command to break down complex tasks into manageable subtasks.
🔄 Regenerate Files
After any updates to tasks.json, regenerate the task files to keep them in sync.
💬 Provide Context
When asking the Cursor agent to help with a task, provide context about what you’re trying to achieve.
✅ Validate Dependencies
Periodically run the validate-dependencies command to check for invalid or circular dependencies.