From task-management
Organizes markdown task files into folders like tasks/, ideas/, templates/, bugs/ with YAML frontmatter defining types (task, idea, bug), due dates, tags, status. Use when creating or modifying task files.
How this skill is triggered — by the user, by Claude, or both
Slash command
/task-management:manage-tasksThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- `tasks/` - Items with specific due dates that need to be completed
tasks/ - Items with specific due dates that need to be completedideas/ - Projects and ideas without due dates (someday/maybe)templates/ - Reusable task templates (e.g., blog post checklist, event prep)memories/ - Reference items and context (not actionable)bugs/ - Issues and problems to fixcompleted/ - Archived one-time tasks that have been finishedimport/ - Temporary folder for reviewing imported items before moving to appropriate foldersEach task is a markdown file with YAML frontmatter:
---
type: task | idea | template | memory | bug
due: YYYY-MM-DD
tags: [tag1, tag2]
---
# Task Title
Task content here.
type - Categorizes the file for organization:
task - Actionable item with due date (goes in tasks/)idea - Project or concept without deadline (goes in ideas/)template - Reusable checklist or structure (goes in templates/)memory - Reference/context item, not actionable (goes in memories/)bug - Issue or problem to fix (goes in bugs/)due: YYYY-MM-DD - Due date (required for tasks, optional for ideas)completed: YYYY-MM-DD - Completion date for finished one-time tasksrecurrence: monthly | quarterly | weekly | biweekly | yearly - For recurring tasksrecurrence_day: N - Day of month for recurring tasksstatus: in-progress | noodling | someday - For idea files only (not used in tasks/)tags: [tag1, tag2] - Categorization tagscompleted: date and move to completed/due: date when complete (never move to completed/)status field to track progress:
in-progress - Actively working on this, but no specific deadline yetnoodling - Thinking about it, exploring, might become in-progresssomeday - Parked for later, not active nowcompleted: date and move to completed/completed: datetype: field during reviewRecurring tasks include:
Example:
---
type: task
due: 2025-01-15
recurrence: monthly
recurrence_day: 15
tags: [admin]
---
# Monthly Report
## Instructions
When completing this task:
1. Update the `due:` date to next month
2. Add completion date to History section
## History
- 2024-12-15: Completed
- 2024-11-15: Completed
CRITICAL: Preserve user's exact text formatting
When the user provides notes, content, or task details:
Just the essentials:
Include:
Include:
Include:
npx claudepluginhub ttorres33/teresa-torres-plugins --plugin task-managementDefines conventions for TASKS.md files: structure with optional sections, status symbols ([ ] todo, [/] ongoing, [x] done, [-] backlog), task descriptions, and testable acceptance criteria. Use for creating, editing, updating tasks or tracking progress.
Manages tasks-plans/ workspace by adding actionable items to backlog, ideas for exploration, or dated references. Organizes files by topic into subfolders, processes queued work via subcommands.
Creates sequential tasks with priority, status, due dates in secondbrain's .claude/data/tasks YAML shards. Activates on 'create task', 'add todo', or similar requests.