plan_task
Register user requests, organize tasks, and manage subtasks with dependencies and notes. Export task plans for reference and ensure structured workflows with user approval at each step for effective task completion.
Instructions
Register a new user request and plan its associated tasks. You must provide 'originalRequest' and 'tasks', and optionally 'splitDetails'.
Tasks can now include subtasks, which are smaller units of work that make up a task. All subtasks must be completed before a task can be marked as done.
You can also include:
- 'dependencies': List of project or task-specific dependencies (libraries, tools, etc.)
- 'notes': General notes about the project (preferences, guidelines, etc.)
- 'outputPath': Path to save a Markdown file with the task plan for reference. It's recommended to use absolute paths (e.g., 'C:/Users/username/Documents/task-plan.md') rather than relative paths for more reliable file creation.
This tool initiates a new workflow for handling a user's request. The workflow is as follows:
- Use 'plan_task' to register a request and its tasks (with optional subtasks, dependencies, and notes).
- After adding tasks, you MUST use 'get_next_task' to retrieve the first task. A progress table will be displayed.
- Use 'get_next_task' to retrieve the next uncompleted task.
- If the task has subtasks, complete each subtask using 'mark_subtask_done' before marking the task as done.
- IMPORTANT: After marking a task as done, a progress table will be displayed showing the updated status of all tasks. The assistant MUST NOT proceed to another task without the user's approval. The user must explicitly approve the completed task.
- Once a task is approved, you can proceed to 'get_next_task' again to fetch the next pending task.
- Repeat this cycle until all tasks are done.
- After all tasks are completed (and approved), 'get_next_task' will indicate that all tasks are done and that the request awaits approval for full completion.
- The user must then approve the entire request's completion. If the user does not approve and wants more tasks, you can again use 'plan_task' to add new tasks and continue the cycle.
The critical point is to always wait for user approval after completing each task and after all tasks are done, wait for request completion approval. Do not proceed automatically.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dependencies | No | ||
| notes | No | ||
| originalRequest | Yes | ||
| outputPath | No | ||
| splitDetails | No | ||
| tasks | Yes |