This skill should be used when the user asks about "tracking task progress", "checkpoint best practices", "incremental commits", "task documentation", "progress logging", "work tracking", or needs guidance on how to document progress in local-docs/todo/ directories, create effective checkpoint entries, or maintain task state across sessions.
Creates progress checkpoints with context-rich documentation for task continuity across sessions.
/plugin marketplace add victor-software-house/task-tracker-plugin/plugin install victor-software-house-task-tracker@victor-software-house/task-tracker-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Effective progress tracking preserves context, enables recovery after compaction, and maintains continuity across sessions. This skill provides patterns for documenting progress in the local-docs/todo/ workflow.
Document progress in small, frequent checkpoints rather than large batches:
Each checkpoint should contain enough context for full recovery:
## YYYY-MM-DD HH:MM:SS
### Summary
[One-line summary of this checkpoint]
### Progress Since Last Checkpoint
- Completed [specific task/subtask]
- Implemented [feature/fix]
- Researched [topic] - found [key insight]
### Key Insights & Decisions
- Decided to use [approach] because [rationale]
- Discovered that [finding] which means [implication]
- Changed strategy from [old] to [new] due to [reason]
### Current State
[Description of where the work stands]
- Files modified: [list]
- Tests status: [passing/failing/pending]
- Dependencies: [resolved/pending]
### Next Steps
1. [Immediate next action]
2. [Following action]
3. [Third priority]
### Context to Preserve
[Any context that would be lost without explicit documentation]
- Working hypothesis: [...]
- Temporary workaround: [...]
- Investigation path: [...]
When modifying code, track:
When investigating or researching:
When debugging issues:
Follow the established workflow conventions:
Tasks execute in order: 01-* → 02-* → 03-*
Track which subtask is current and what's next.
local-docs/todo/NN-task-name/
├── 00-index.md # Task overview (update status here)
├── 01-phase-one.md # Phase documentation
├── 02-phase-two.md
├── CHECKPOINT-LOG.md # Progress checkpoints
├── .changes.log # Auto-tracked file changes
└── .operations.log # Auto-tracked operations
Commit after each subtask completion:
git -C local-docs commit -m "checkpoint: [task] - [brief description]"
After session restart or compaction:
/resume-task [name] to load context/checkpoint [summary] - Create progress checkpoint/task-status - View current task state/resume-task [name] - Load task context/set-task [name] - Set active taskApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.