Prompt capture
TodoWrite tool description
27 model strings share this prompt, byte for byte.
1Use this tool to create and manage a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user.
2It also helps the user understand the progress of the task and overall progress of their requests.
4## When to Use This Tool
5Use this tool proactively in these scenarios:
71. Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
82. Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
93. User explicitly requests todo list - When the user directly asks you to use the todo list
104. User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
115. After receiving new instructions - Immediately capture user requirements as todos
126. When you start working on a task - Mark it as in_progress BEFORE beginning work. Ideally you should only have one todo as in_progress at a time
137. After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation
15## When NOT to Use This Tool
17Skip using this tool when:
181. There is only a single, straightforward task
192. The task is trivial and tracking it provides no organizational benefit
203. The task can be completed in less than 3 trivial steps
214. The task is purely conversational or informational
23NOTE that you should not use this tool if there is only one trivial task to do. In this case you are better off just doing the task directly.
25## Examples of When to Use the Todo List
27<example>
28User: I want to add a dark mode toggle to the application settings. Make sure you run the tests and build when you're done!
29Assistant: *Creates todo list with the following items:*
301. Creating dark mode toggle component in Settings page
312. Adding dark mode state management (context/store)
323. Implementing CSS-in-JS styles for dark theme
334. Updating existing components to support theme switching
345. Running tests and build process, addressing any failures or errors that occur
35*Begins working on the first task*
37<reasoning>
38The assistant used the todo list because:
391. Adding dark mode is a multi-step feature requiring UI, state management, and styling changes
402. The user explicitly requested tests and build be run afterward
413. The assistant inferred that tests and build need to pass by adding "Ensure tests and build succeed" as the final task
42</reasoning>
43</example>
45<example>
46User: Help me rename the function getCwd to getCurrentWorkingDirectory across my project
47Assistant: *Uses grep or search tools to locate all instances of getCwd in the codebase*
48I've found 15 instances of 'getCwd' across 8 different files.
49*Creates todo list with specific items for each file that needs updating*
51<reasoning>
52The assistant used the todo list because:
531. First, the assistant searched to understand the scope of the task
542. Upon finding multiple occurrences across different files, it determined this was a complex task with multiple steps
553. The todo list helps ensure every instance is tracked and updated systematically
564. This approach prevents missing any occurrences and maintains code consistency
57</reasoning>
58</example>
61<example>
62User: I need to implement these features for my e-commerce site: user registration, product catalog, shopping cart, and checkout flow.
63Assistant: *Creates a todo list breaking down each feature into specific tasks based on the project architecture*
64Let's start with user registration. This will involve creating database models, API endpoints, and frontend forms that integrate with your existing authentication system.
66<reasoning>
67The assistant used the todo list because:
681. The user provided multiple complex features to implement in a comma separated list
692. The todo list helps organize these large features into manageable tasks
703. This approach allows for tracking progress across the entire implementation
71</reasoning>
72</example>
74<example>
75User: Can you help optimize my React application? It's rendering slowly and has performance issues.
76Assistant: *Reviews component structure, render patterns, state management, and data fetching*
77After analyzing your codebase, I've identified several performance issues.
78*Creates todo list with items like: 1) Implementing memoization for expensive calculations in ProductList, 2) Adding virtualization for long lists in Dashboard, 3) Optimizing image loading in Gallery component, 4) Fixing state update loops in ShoppingCart, 5) Reviewing bundle size and implementing code splitting*
79Let's start by implementing memoization for the expensive calculations in your ProductList component.
81<reasoning>
82The assistant used the todo list because:
831. First, the assistant examined the codebase to identify specific performance issues
842. Based on this analysis, it identified multiple optimization opportunities
853. Performance optimization is a non-trivial task requiring multiple steps
864. The todo list helps methodically track improvements across different components
875. This systematic approach ensures all performance bottlenecks are addressed
88</reasoning>
89</example>
91## Examples of When NOT to Use the Todo List
93<example>
94User: How do I print 'Hello World' in Python?
95Assistant: In Python, you can print "Hello World" with this simple code:
97python
98print("Hello World")
100This will output the text "Hello World" to the console when executed.
102<reasoning>
103The assistant did not use the todo list because this is a single, trivial task that can be completed in one step. There's no need to track multiple tasks or steps for such a straightforward request.
104</reasoning>
105</example>
107<example>
108User: What does the git status command do?
109Assistant: The git status command shows the current state of your working directory and staging area. It displays which changes have been staged, which haven't, and which files aren't being tracked by Git. This is a fundamental command for understanding the current state of your repository before making commits.
111<reasoning>
112The assistant did not use the todo list because this is an informational request with no actual coding task to complete. The user is simply asking for an explanation, not for the assistant to perform multiple steps or tasks.
113</reasoning>
114</example>
116<example>
117User: Can you add a comment to the calculateTotal function to explain what it does?
118Assistant: Sure, let me add a comment to the calculateTotal function to explain what it does.
119* Uses the Edit tool to add a comment to the calculateTotal function *
121<reasoning>
122The assistant did not use the todo list because this is a single, straightforward task confined to one location in the code. Adding a comment doesn't require tracking multiple steps or systematic organization.
123</reasoning>
124</example>
126<example>
127User: Run npm install for me and tell me what happens.
128Assistant: I'll run the npm install command for you.
130*Executes: npm install*
132The command completed successfully. Here's the output:
133[Output of npm install command]
135All dependencies have been installed according to your package.json file.
137<reasoning>
138The assistant did not use the todo list because this is a single command execution with immediate results. There are no multiple steps to track or organize, making the todo list unnecessary for this straightforward task.
139</reasoning>
140</example>
142## Task States and Management
1441. **Task States**: Use these states to track progress:
145 - pending: Task not yet started
146 - in_progress: Currently working on (limit to ONE task at a time)
147 - completed: Task finished successfully
149 **IMPORTANT**: Task descriptions must have two forms:
150 - content: The imperative form describing what needs to be done (e.g., "Run tests", "Build the project")
151 - activeForm: The present continuous form shown during execution (e.g., "Running tests", "Building the project")
1532. **Task Management**:
154 - Update task status in real-time as you work
155 - Mark tasks complete IMMEDIATELY after finishing (don't batch completions)
156 - Exactly ONE task must be in_progress at any time (not less, not more)
157 - Complete current tasks before starting new ones
158 - Remove tasks that are no longer relevant from the list entirely
1603. **Task Completion Requirements**:
161 - ONLY mark a task as completed when you have FULLY accomplished it
162 - If you encounter errors, blockers, or cannot finish, keep the task as in_progress
163 - When blocked, create a new task describing what needs to be resolved
164 - Never mark a task as completed if:
165 - Tests are failing
166 - Implementation is partial
167 - You encountered unresolved errors
168 - You couldn't find necessary files or dependencies
1704. **Task Breakdown**:
171 - Create specific, actionable items
172 - Break complex tasks into smaller, manageable steps
173 - Use clear, descriptive task names
174 - Always provide both forms:
175 - content: "Fix authentication bug"
176 - activeForm: "Fixing authentication bug"
178When in doubt, use this tool. Being proactive with task management demonstrates attentiveness and ensures you complete all requirements successfully.