File-Based Task Tracking
Manages a file-based todo tracking system for code review feedback, technical debt, and feature requests.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Manages complex task dependencies by linking todo items via their issue IDs in the frontmatter.
- Integrates with developer workflows and provides quick reference shell commands for efficient task management.
- Enforces detailed record-keeping through a chronological 'Work Log' in each todo file.
- Defines a structured format for todo files, including YAML frontmatter and required sections like Problem Statement and Acceptance Criteria.
- Provides clear workflows for the entire task lifecycle, from creation and triage (pending) to approval (ready) and completion.
Use cases
- Triage and manage a backlog of pending development tasks, approving them for implementation.
- Convert code review comments or technical debt findings into formally tracked and prioritized work items.
- Document the investigation, proposed solutions, and resolution process for a complex bug or feature.
FAQ
What does the File-Based Task Tracking skill do?
This skill enables Claude to manage a structured, file-based todo system directly in your code repository. It helps create, triage, and track tasks like technical debt, feature requests, and code review feedback using markdown files with YAML frontmatter.
How does this skill improve my workflow?
It integrates task management directly into your codebase, eliminating context switching. The skill enforces detailed record-keeping with work logs, manages complex dependencies between tasks, and provides shell commands for quick access, streamlining your development lifecycle.
When should I use this skill?
Use this skill for any development task that requires more than 15-20 minutes, needs planning, has dependencies, or requires formal approval. It's ideal for converting code review comments or complex bugs into actionable, tracked items.
What key features does this skill provide?
It provides a structured markdown/YAML format for todos, a clear lifecycle workflow (pending, ready, complete), issue ID-based dependency management, a chronological work log for each task, and seamless integration with command-line developer workflows.
Related skills
DRY Code Refactoring
Refactors duplicate code by applying DRY (Don't Repeat Yourself) principles and common abstraction techniques.
Developer Tools5812 ptsSmalltalk Implementation Finder
Finds and analyzes method implementations across Pharo Smalltalk class hierarchies to understand code patterns and assess refactoring impact.
Developer Tools112 ptsCode Review Workflow
Executes a comprehensive code review by running parallel automated and architectural analyses, then systematically applies the recommended improvements.
Developer Tools12 pts