check-todos — Claude Code command: task list and workflow selection
check-todos — a command to view outstanding tasks from TO-DOS.md and pick one to work on. Streamlines task selection by matching work to project workflows and inviting the right skill if available.
MIT ★ 1,988 updated 2026-04-01
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resourcesWhat check-todos does
The command scans TO-DOS.md for active items (lines starting with - **), displays them in a numbered list with timestamps, and prompts you to select one. After selection, it shows the full task context—all fields (problem, files, solution), a brief summary of related files, and checks CLAUDE.md and .claude/skills/ for a matching workflow.
When a workflow fits (such as plugin or MCP work), the command offers to invoke the skill. Otherwise it presents options: start work, brainstorm first, or browse other tasks. Starting work removes the task from TO-DOS.md; choosing brainstorm calls /brainstorm. Requires Read, Edit, and Glob tools to access the file system.
What it helps with
- keep track of open tasks in a single file
- jump to the next task without manual file hunting
- match task type to the right skill or workflow
- remove completed tasks from TO-DOS.md automatically
Example prompts for the agent
- /check-todos
- Show me all tasks and help me pick one to start
- Select a task and begin work with the matching skill
How to install check-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/check-todos.mdCall it with /check-todos. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/check-todos.mdCall it with /prompts:check-todos. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/check-todos.prompt.mdManually: put the files in place
.gemini/commands/check-todos.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about check-todos
How do I install check-todos in Claude Code?
Run in order: /plugin marketplace add glittercowboy/taches-cc-resources, then /plugin install taches-cc-resources@taches-cc-resources, and place the .claude/commands/check-todos.md file in your project.
What does check-todos do?
It lists active tasks from TO-DOS.md, lets you select one, displays its full details, and offers to start work or brainstorm. Starting work removes the task from the file.
What do I need for check-todos to work?
Your project needs a TO-DOS.md file with active tasks formatted as - **task name**. The command looks for CLAUDE.md and .claude/skills/ to detect project rules and applicable workflows.
Source text
check-todos.md · MIT
---
description: List outstanding todos and select one to work on
allowed-tools:
- Read
- Edit
- Glob
---
# Check Todos
## Instructions
1. Read TO-DOS.md in the working directory (if doesn't exist, say "No outstanding todos" and exit)
2. Parse and display todos:
- Extract all list items starting with `- **` (active todos)
- If none exist, say "No outstanding todos" and exit
- Display compact numbered list showing:
- Number (for selection)
- Bold title only (part between `**` markers)
- Date from h2 heading above it
- Prompt: "Reply with the number of the todo you'd like to work on."
- Wait for user to reply with a number
3. Load full context for selected todo:
- Display complete line with all fields (Problem, Files, Solution)
- Display h2 heading (topic + date) for additional context
- Read and briefly summarize relevant files mentioned
4. Check for established workflows:
- Read CLAUDE.md (if exists) to understand project-specific workflows and rules
- Look for `.claude/skills/` directory
- Match file paths in todo to domain patterns (`plugins/` → plugin workflow, `mcp-servers/` → MCP workflow)
- Check CLAUDE.md for explicit workflow requirements for this type of work
5. Present action options to user:
- **If matching skill/workflow found**: "This looks like [domain] work. Would you like to:\n\n1. Invoke [skill-name] skill and start\n2. Work on it directly\n3. Brainstorm approach first\n4. Put it back and browse other todos\n\nReply with the number of your choice."
- **If no workflow match**: "Would you like to:\n\n1. Start working on it\n2. Brainstorm approach first\n3. Put it back and browse other todos\n\nReply with the number of your choice."
- Wait for user response
6. Handle user choice:
- **Option "Invoke skill" or "Start working"**: Remove todo from TO-DOS.md (and h2 heading if section becomes empty), then begin work (invoke skill if applicable, or proceed directly)
- **Option "Brainstorm approach"**: Keep todo in file, invoke `/brainstorm` with the todo description as argument
- **Option "Put it back"**: Keep todo in file, return to step 2 to display the full list again
## Display Format
```
Outstanding Todos:
1. Add structured format to add-to-todos (2025-11-15 14:23)
2. Create check-todos command (2025-11-15 14:23)
3. Fix cookie-extractor MCP workflow (2025-11-14 09:15)
Reply with the number of the todo you'd like to work on.
```
© Lex Christopherson · MIT · glittercowboy/taches-cc-resources