Stats
Actions
Tags
From lucas-dev-tools
This skill should be used when the user wants to create or append tasks to TODO.md — triggered by phrases like 'add todo', 'add a task', 'TODO:', 'new task', 'track this', 'note this down', 'add to the backlog', 'before I forget', or any variation of wanting to capture new items. Also applies when the user finishes work and mentions follow-up items to save for later. Not appropriate for reading, viewing, checking off, removing, or reorganizing TODO.md.
How this skill is triggered — by the user, by Claude, or both
Slash command
/lucas-dev-tools:add-todoThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Add one or more tasks to TODO.md in the current working directory.
Add one or more tasks to TODO.md in the current working directory.
Identify the task(s) the user wants to add from their message. If the request is vague, ask a brief clarifying question — but if the intent is clear enough, just proceed.
If the task references codebase artifacts, do minimal research (1-2 tool calls) to include useful context in the TODO entry. For example, if the user says "add a task to refactor the auth module", skim relevant source files to note key file paths and considerations. Skip research for self-contained tasks that need no codebase context. This context helps whoever picks up the task later (via the whats-next skill or otherwise) get started quickly without re-discovering the same information.
Add each task as a single item. Do not break tasks into sub-items unless the user explicitly requests it.
If TODO.md exists, read it to understand the current format (checkbox style, numbered list, headings, etc.) and where new items should go. Preserve the existing format exactly.
If TODO.md does not exist, create it with this default format:
# TODO
- [ ] <task>
Add the new item(s) to the end of the list, matching the file's existing format. If there are section headings, infer the appropriate section from context; if ambiguous, add to the last section.
Before adding, check for existing items that are very similar to avoid duplicates. If a near-duplicate exists, inform the user and ask whether to add anyway or skip.
Mark new items as incomplete (e.g., - [ ] for checkbox format). Include the research context gathered in Step 1 as indented sub-bullets under the main task entry.
Briefly confirm what was added — e.g., "Added 2 tasks to TODO.md." Keep it short.
npx claudepluginhub lucaspimentel/claude-plugins --plugin lucas-dev-toolsCreates tasks or sections in TASKS.md to track project work. Auto-triggers on phrases like 'add a task', 'todo', 'let's plan', or untracked future work.
Creates and manages structured Markdown todos for code reviews, technical debt, work items, and findings in .context/compound-engineering/todos/, handling lifecycle from pending to complete.
Picks the next executable task from project-root TODO.md by priority and dependency, marks it in-progress, and executes it. Uses a structured task format with priority, ID, and dep fields.