add-to-todos — Claude Code command: what it does, how to install
add-to-todos appends tasks to TO-DOS.md with conversation context, file references, and line numbers without derailing ongoing work.
MIT ★ 1,988 updated 2026-04-01
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resourcesWhat add-to-todos does
The command manages TO-DOS.md in the working directory, creating the file if it is missing. When invoked with an argument, it uses that input as the title. If executed without arguments, it extracts task details from recent messages, gathering the core issue, affected file paths, line ranges, and error notes.
Before writing to disk, it checks existing tasks for duplicate concepts. If an overlap turns up, Claude pauses and asks whether to skip, replace the older entry, or add it anyway. Each item gets a timestamped header and inline labels for Problem, Files, and an optional Solution. Markdown checkboxes are omitted because items are intended for deletion once implementation starts.
The command requires tool access for Read, Edit, and Write. After appending the entry, Claude confirms the save and immediately prompts to continue the task you were working on before the call.
What it helps with
- append technical issues to
TO-DOS.mdwith exact file line numbers - extract task context from conversation history without manual writing
- prevent duplicate action items in project task logs
- resume uninterrupted coding immediately after capturing a side note
Example prompts for the agent
- /add-to-todos extract auth token refresh into background worker
- /add-to-todos
How to install add-to-todos
1Plugin marketplace
/plugin marketplace add glittercowboy/taches-cc-resources/plugin install taches-cc-resources@taches-cc-resources2Manually: put the files in place
.claude/commands/add-to-todos.mdCall it with /add-to-todos. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/add-to-todos.mdCall it with /prompts:add-to-todos. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/add-to-todos.prompt.mdManually: put the files in place
.gemini/commands/add-to-todos.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about add-to-todos
How to install add-to-todos in Claude Code?
Run /plugin marketplace add glittercowboy/taches-cc-resources and then /plugin install taches-cc-resources@taches-cc-resources. Alternatively, place the file directly at .claude/commands/add-to-todos.md.
What does add-to-todos do?
It writes a structured task entry into TO-DOS.md, recording the problem description, file paths with line ranges, and potential solutions straight from the active session.
How does add-to-todos handle existing tasks?
It checks TO-DOS.md for matching scope or titles and prompts you to skip, replace the existing item, or create a separate entry.
Source text
add-to-todos.md · MIT
---
description: Add todo item to TO-DOS.md with context from conversation
argument-hint: <todo-description> (optional - infers from conversation if omitted)
allowed-tools:
- Read
- Edit
- Write
---
# Add Todo Item
## Context
- Current timestamp: !`date "+%Y-%m-%d %H:%M"`
## Instructions
1. Read TO-DOS.md in the working directory (create with Write tool if it doesn't exist)
2. Check for duplicates:
- Extract key concept/action from the new todo
- Search existing todos for similar titles or overlapping scope
- If found, ask user: "A similar todo already exists: [title]. Would you like to:\n\n1. Skip adding (keep existing)\n2. Replace existing with new version\n3. Add anyway as separate item\n\nReply with the number of your choice."
- Wait for user response before proceeding
3. Extract todo content:
- **With $ARGUMENTS**: Use as the focus/title for the todo and context heading
- **Without $ARGUMENTS**: Analyze recent conversation to extract:
- Specific problem or task discussed
- Relevant file paths that need attention
- Technical details (line numbers, error messages, conflicting specifications)
- Root cause if identified
4. Append new section to bottom of file:
- **Heading**: `## Brief Context Title - YYYY-MM-DD HH:MM` (3-8 word title, current timestamp)
- **Todo format**: `- **[Action verb] [Component]** - [Brief description]. **Problem:** [What's wrong/why needed]. **Files:** [Comma-separated paths with line numbers]. **Solution:** [Approach hints or constraints, if applicable].`
- **Required fields**: Problem and Files (with line numbers like `path/to/file.ts:123-145`)
- **Optional field**: Solution
- Make each section self-contained for future Claude to understand weeks later
- Use simple list items (not checkboxes) - todos are removed when work begins
5. Confirm and offer to continue with original work:
- Identify what the user was working on before `/add-to-todos` was called
- Confirm the todo was saved: "✓ Saved to todos."
- Ask if they want to continue with the original work: "Would you like to continue with [original task]?"
- Wait for user response
## Format Example
```markdown
## Add Todo Command Improvements - 2025-11-15 14:23
- **Add structured format to add-to-todos** - Standardize todo entries with Problem/Files/Solution pattern. **Problem:** Current todos lack consistent structure, making it hard for Claude to have enough context when revisiting tasks later. **Files:** `commands/add-to-todos.md:22-29`. **Solution:** Use inline bold labels with required Problem and Files fields, optional Solution field.
- **Create check-todos command** - Build companion command to list and select todos. **Problem:** Need workflow to review outstanding todos and load context for selected item. **Files:** `commands/check-todos.md` (new), `TO-DOS.md` (reads from). **Solution:** Parse markdown list, display numbered list, accept selection to load full context and remove item.
```
© Lex Christopherson · MIT · glittercowboy/taches-cc-resources