todo-list

Display a summary of all active todos, sorted by priority and due date, with options to take action on specific items.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "todo-list" with this command: npx skills add legacybridge-tech/claude-plugins/legacybridge-tech-claude-plugins-todo-list

Todo List

Purpose

Display a summary of all active todos, sorted by priority and due date, with options to take action on specific items.

Execution Flow

Phase 1: Locate Todos Directory

  • Search for Todos/ directory in the current working directory or its parents

  • Check Todos/active/ for todo files

  • If not found: "No Todos directory found. You can create one using /todo-add."

Phase 2: Read Active Todos

Use Glob to find all .md files in Todos/active/ :

Todos/active/*.md

(Exclude README.md)

For each todo file, read and parse frontmatter:

  • title

  • status

  • priority

  • due_date

  • created_at

  • source_file

  • dependencies

Phase 3: Sort Todos

Sort order (primary to tertiary):

  • Priority: high → medium → low

  • Due Date: overdue → today → this week → later → no date

  • Created Date: oldest first (to surface forgotten items)

Phase 4: Format Output

Display as formatted table:

Active Todos

#TitlePriorityDueStatusSource
1Reply to client email🔴 High2025-01-15 (2 days)pendingemail
2Review design docs🟡 Medium2025-01-20in_progress-
3Update documentation🟢 Low-pending-

Summary

  • Total: 3 active todos
  • High Priority: 1
  • Overdue: 0
  • Blocked: 0 (dependencies not met)

Overdue Items

(none)

Due Today

(none)

Due This Week

  • Reply to client email (2025-01-15)

Phase 5: Display Status Legend

Status:

  • pending: Not started
  • in_progress: Currently working on
  • blocked: Waiting for dependencies

Priority:

  • 🔴 High: Urgent/time-sensitive
  • 🟡 Medium: Normal priority
  • 🟢 Low: When time permits

Phase 6: Offer Actions

Ask user what they want to do next:

{ "question": "What would you like to do?", "header": "Actions", "options": [ {"label": "View details of a todo", "description": "Read the full content of a specific todo"}, {"label": "Mark a todo complete", "description": "Complete and archive a todo"}, {"label": "Update a todo", "description": "Change priority, due date, or status"}, {"label": "Nothing, just viewing", "description": "Close this view"} ], "multiSelect": false }

If user selects an action, follow up with todo selection:

{ "question": "Which todo?", "header": "Select Todo", "options": [ {"label": "#1 Reply to client email", "description": "High priority, due 2025-01-15"}, {"label": "#2 Review design docs", "description": "Medium priority, in progress"}, {"label": "#3 Update documentation", "description": "Low priority, no deadline"} ], "multiSelect": false }

Output Formats

Standard View (default)

Table format as shown above.

Compact View

If there are many todos (>10):

Active Todos (15 items)

🔴 High Priority (3)

  1. Reply to client email - due 2025-01-15
  2. Fix critical bug - due today ⚠️
  3. Submit report - overdue ❌

🟡 Medium Priority (7)

  1. Review design docs - in progress
  2. Update API docs ...

🟢 Low Priority (5)

  1. Refactor utils ...

Blocked Items

If any todos have unmet dependencies:

⏸️ Blocked Todos

  • Prepare client presentation (blocked) Waiting for: Review design docs, Get approval

Empty State

If no active todos:

Active Todos

No active todos! 🎉

You can:

  • Add a new todo with /todo-add
  • Check completed todos in Todos/completed/

Error Handling

Corrupted Frontmatter

If a todo file has invalid frontmatter:

  • Log warning: "Warning: [filename] has invalid frontmatter"

  • Skip the file in listing

  • Mention at the end: "1 todo file could not be parsed"

Missing Directory

If Todos/active/ doesn't exist but Todos/ does:

  • Offer to create the directory structure

  • Or report "No active todos found"

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

tailwindplus

No summary provided by upstream source.

Repository SourceNeeds Review
General

process-file

No summary provided by upstream source.

Repository SourceNeeds Review
General

initialize-project

No summary provided by upstream source.

Repository SourceNeeds Review