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
More from legacybridge-tech/claude-plugins
process-file
Process arbitrary files (email, PDF, Office docs, images, audio/video) and integrate with AkashicRecords for intelligent archiving. Reads file content, analyzes intent, and suggests appropriate storage location based on content and project preferences.
16multi-perspective-analysis
Analyze propositions from multiple expert perspectives. Dynamically generates 4-6 relevant expert roles, then performs validation, comprehensive analysis, or debate-style examination. Use when user wants to examine ideas critically, find blindspots, or explore different viewpoints on a topic.
16tailwindplus
Access TailwindPlus UI component library - search, list, and retrieve code for Marketing, Application UI, and eCommerce components in HTML/React/Vue with Tailwind CSS v3/v4
12gemini
Use Google Gemini API for text generation, multimodal analysis, image generation (Nano Banana), function calling, and search grounding. Invoke when user wants to use Gemini, ask Gemini, generate images with Gemini, or analyze content with Gemini.
7communication-tracker
Track and integrate external communications (emails, chat messages, screenshots) into project context with timeline management. Use when user mentions "email", "message", "communication", "screenshot", "track", "import", "sync", or wants to import external information sources into the project timeline.
7initialize-project
Initialize a new software project with customized structure through interactive Q&A. Use when user mentions "new project", "start project", "initialize project", "create project", or "set up project". Gathers methodology, team structure, documentation preferences, and integration requirements to generate appropriate RULE.md and directory structure.
7