Best Practices
Task hierarchy design:
Project (parent)
└── Feature A (child)
├── Component A1 (leaf task)
│ ├── Implementation
│ └── Tests (depends on Implementation)
└── Component A2Dependency management:
- Always define dependencies when creating tasks
- Use task IDs (not titles) for dependency references
- Verify dependencies with
TaskGetbefore execution
Status transitions:
- Mark
in_progresswhen starting work (prevents parallel execution) - Update frequently for visibility
- Only mark
completedwhen fully accomplished (tests passing, validated) - Use
failedstatus with error metadata for debugging
Metadata conventions:
json
{
"priority": "high|medium|low",
"estimated_duration": "2h",
"related_files": ["path/to/file.ts"],
"related_issue": "https://github.com/org/repo/issues/123",
"type": "feature|bugfix|refactor|test"
}