todo
Manage project todos in todos.md file
- 0
- Installs
- —
- Rating
- —
- Success rate
- 1
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 383a222ee9f8338b… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
todo.md
Project Todo Manager
Manage todos in a todos.md file at the root of your current project directory: $ARGUMENTS
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.
Files
1- todo.md
12143423863.0 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from davila7/claude-code-templates8
Execute GitHub Actions locally using act
Implement secure user authentication system with chosen method and security best practices
Generate and maintain project changelog with Keep a Changelog format
Setup comprehensive mutation testing with framework selection and CI integration
Add and configure new package to workspace with proper structure and dependencies
Setup comprehensive application performance monitoring with metrics, alerting, and observability
Implement property-based testing with framework selection and invariant identification
Add entry to project changelog following Keep a Changelog format
Related frontend skillsscan passed
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding,
Guided end-to-end plugin creation workflow with component design, implementation, and validation
Audit UI code for WCAG compliance
Initialize Nuxt UI v4 in an existing Nuxt project with proper configuration