Project Task Manager
AI-powered task generation and project management tool. Break down objectives into structured, hierarchical task trees with dependencies, priorities, and time estimates. Track progress as you work through tasks.
Actions
generate
Create a hierarchical task breakdown from a high-level objective. An AI model analyzes your objective and produces a structured tree of tasks with dependencies, time estimates, and priorities.
Required fields:
action:"generate"objective(string): What you want to accomplish. Be specific about the end goal. Max 2000 characters.
Optional fields:
context(object): Technologies or constraints. Example:{"tech": ["python", "postgresql"], "constraints": ["must use docker", "deploy to AWS"]}max_depth(integer, 1-4): How many levels deep to break down tasks. 2 = simple, 3 = standard (default), 4 = very detailed.
Example:
{
"action": "generate",
"objective": "Build a REST API for user management with JWT authentication",
"context": {"tech": ["python", "fastapi"], "constraints": ["must use PostgreSQL"]},
"max_depth": 3
}
Response includes: tree_id (save this for future actions), task_ids (list of all task IDs), tasks (full hierarchy), total_tasks, estimated_total_time (minutes), and dependency_graph.
update
Mark progress on a specific task within a task tree. Use this as you start, complete, or get blocked on tasks.
Required fields:
action:"update"tree_id(string): The tree_id returned from the generate action.task_id(string): The specific task_id to update (from the generate response task_ids list).
At least one of these is required:
status(string): New status. One of:"pending","in_progress","completed","failed","blocked".progress(number, 0-100): Completion percentage. 0 = not started, 50 = halfway, 100 = done.notes(string): What happened or what you discovered. Max 500 characters.
Example:
{
"action": "update",
"tree_id": "abc-123-def",
"task_id": "task-456",
"status": "in_progress",
"progress": 25,
"notes": "Started implementing the database schema"
}
Response includes: updates_applied, new_progress (overall tree progress), and tasks_remaining.
decompose
Break a single task description into smaller, actionable subtasks. This is a standalone operation that does not require an existing task tree.
Required fields:
action:"decompose"task(string): The task to break into smaller steps. Be specific.
Optional fields:
level_of_detail(string): How detailed the breakdown should be. One of:"basic"(3-5 steps),"standard"(5-10 steps, default),"detailed"(10-15 steps).
Example:
{
"action": "decompose",
"task": "Implement user login with session management and password reset",
"level_of_detail": "detailed"
}
Response includes: subtasks (list with name, description, estimated_time, dependencies, and tools for each), total_subtasks.
status
Check the current progress and status of a task tree.
Required fields:
action:"status"tree_id(string): The tree_id returned from the generate action.
Example:
{
"action": "status",
"tree_id": "abc-123-def"
}
Response includes: overall_progress (percentage), completed_tasks, total_tasks, current_tasks (in-progress tasks), blocked_tasks, estimated_completion, and last_updated.
list
Show all your task trees, sorted by most recently updated. Returns up to 50 trees.
Required fields:
action:"list"
Example:
{
"action": "list"
}
Response includes: trees (list with tree_id, objective, task_count, progress, created_at, updated_at for each), total.
Common Workflows
Plan and Execute a Project
- Use
generatewith your objective to create a task tree. Save the returnedtree_idandtask_ids. - Use
statuswith thetree_idto review the plan. - Use
updateto mark tasks as"in_progress"when you start them. - Use
updateto mark tasks as"completed"when finished, or"blocked"/"failed"if issues arise. - Use
statusperiodically to check overall progress.
Quick Task Breakdown
Use decompose when you just need to break a single task into steps without creating a full project tree. Good for ad-hoc planning.
Resume Previous Work
Use list to find your existing task trees, then status with the relevant tree_id to see where you left off.
Important Notes
- The
tree_idreturned fromgenerateis required for allupdateandstatuscalls. Always save it. - Task IDs come from the
task_idsarray in the generate response. Use these exact IDs when callingupdate. - Setting status to
"completed"automatically sets progress to 100%. - Time estimates are in minutes.
- The
decomposeaction is independent and does not create or modify task trees. - Task trees are stored per user and persist between sessions.







