Task Manager Skill
Manage development tasks with persistence across Claude Code sessions using markdown files in docs/tasks/.
Session Workflow
At Session Start
- •Check
docs/tasks/for existing task files - •If user's request matches an existing task → read it, resume from "Left Off At"
- •If no match → create new task file before starting work
During Work
- •Update task file when significant progress is made
- •Log failed approaches in "Attempts" section (prevents retry loops)
- •Keep "Left Off At" current
At Session End
- •ALWAYS update task file with:
- •What was accomplished
- •Exact stopping point
- •What's next
On Task Completion
- •Move file to
docs/tasks/completed/
Task File Location
- •Active tasks:
docs/tasks/[descriptive-name].md - •Completed tasks:
docs/tasks/completed/[descriptive-name].md
Template
See templates/task-file.md for the full template.
Rules
- •One task per file - don't combine unrelated work
- •Descriptive names - use kebab-case (e.g.,
chart-legend-fix.md) - •Never skip the Attempts log - failed approaches are valuable context
- •Be specific in "Left Off At" - a new session should resume without asking questions
- •Done criteria must be testable - not vague like "works correctly"