add-to-todos
The add-to-todos command appends task items to a TO-DOS.md file, extracting context from the current conversation or from user-provided arguments. It checks for duplicate todos before adding, captures relevant file paths with line numbers and technical details, timestamps each entry, and confirms successful save while offering to resume the user's previous work.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/glittercowboy/taches-cc-resources/HEAD/commands/add-to-todos.md -o ~/.claude/commands/add-to-todos.mdadd-to-todos.md
# 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.
```Expert skill auditor for Claude Code Skills. Use when auditing, reviewing, or evaluating SKILL.md files for best practices compliance. MUST BE USED when user asks to audit a skill.
Expert slash command auditor for Claude Code slash commands. Use when auditing, reviewing, or evaluating slash command .md files for best practices compliance. MUST BE USED when user asks to audit a slash command.
Expert subagent auditor for Claude Code subagents. Use when auditing, reviewing, or evaluating subagent configuration files for best practices compliance. MUST BE USED when user asks to audit a subagent.
Gather requirements through adaptive questioning before executing any task
Heal skill documentation by applying corrections discovered during execution with approval workflow
Audit slash command file for YAML, arguments, dynamic context, tool restrictions, and content quality
Audit subagent configuration for role definition, prompt quality, tool selection, XML structure compliance, and effectiveness
List outstanding todos and select one to work on