todo
Manage project todos in todos.md file.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- todo
- origin
- awesome-claude-code
- description
- Manage project todos in todos.md file.
03 SKILL.md 正文
name: todo description: Manage project todos in todos.md file
Project Todo Manager
Manage todos in a todos.md file at the root of your current project directory.
Usage Examples:
/user:todo add "Fix navigation bug"/user:todo add "Fix navigation bug" [date/time/"tomorrow"/"next week"]an optional 2nd parameter to set a due date/user:todo complete 1/user:todo remove 2/user:todo list/user:todo undo 1
Instructions:
You are a todo manager for the current project. When this command is invoked:
- Determine the project root by looking for common indicators (.git, package.json, etc.)
- Locate or create
todos.mdin the project root - Parse the command arguments to determine the action:
add "task description"- Add a new todoadd "task description" [tomorrow|next week|4 days|June 9|12-24-2025|etc...]- Add a new todo with the provided due datedue N [tomorrow|next week|4 days|June 9|12-24-2025|etc...]- Mark todo N with the due date providedcomplete N- Mark todo N as completed and move from the ##Active list to the ##Completed listremove N- Remove todo N entirelyundo N- Mark completed todo N as incompletelist [N]or no args - Show all (or N number of) todos in a user-friendly format, with each todo numbered for referencepast due- Show all of the tasks which are past due and still activenext- Shows the next active task in the list, this should respect Due dates, if there are any. If not, just show the first todo in the Active list
Todo Format:
Use this markdown format in todos.md:
# Project Todos
## Active
- [ ] Task description here | Due: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
- [ ] Another task
## Completed
- [x] Finished task | Done: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
- [x] Another completed task | Due: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified) | Done: MM-DD-YYYY (conditionally include HH:MM AM/PM, if specified)
Behavior:
- Number todos when displaying (1, 2, 3...)
- Keep completed todos in a separate section
- Todos do not need to have Due Dates/Times
- Keep the Active list sorted descending by Due Date, if there are any; though in a list with mixed tasks with and without Due Dates, those with Due Dates should come before those without Due Dates
- If todos.md doesn't exist, create it with the basic structure
- Show helpful feedback after each action
- Handle edge cases gracefully (invalid numbers, missing file, etc.)
- All provided dates/times should be saved/formatted in a standardized format of MM/DD/YYYY (or DD/MM/YYYY depending on locale), unless the user specifies a different format
- Times should not be included in the due date format unless requested (
due N in 2 hoursshould be MM/DD/YYYY @ [+ 2 hours from now])
Always be concise and helpful in your responses.
04 同仓库更多 Skills
higgsfield-skills
暂无简介
cutaway
暂无简介
cracked
暂无简介
spec
Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "write the spec for...", "new spec", "bug: ...", "amend §V.3", "distill spec from code", "spec this idea". Reads and follows FORMAT.md for the caveman encoding rules and pipe-table shape of §T and §B.
check
Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec", "does the code still match §V", "check invariants", "spec vs code".
backprop
Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.