When should I create a todo instead of just fixing the code?

You should create a todo if the work requires more than 15-20 minutes, needs architectural planning, has external dependencies, or requires team triage and prioritization.

How are dependencies between tasks managed?

Dependencies are defined in the YAML frontmatter of each todo file using issue IDs. The skill provides workflows to check for blockers and identify work that is ready to start once dependencies are resolved.

How does this differ from simple TODO comments in code?

Unlike inline comments, this system provides structured fields for problem statements, proposed solutions, dependency tracking, and detailed work logs, making it suitable for complex tasks that require planning.

Is this system compatible with multiple developers?

Yes. Because it uses standard Markdown files in a dedicated directory, the system is version-controlled via Git, allowing team members to review, update, and collaborate on tasks using standard PR workflows.

File-Based Todo Manager

Name: File-Based Todo Manager
Author: RBozydar

byRBozydar

생산성 및 워크플로

Manages a structured, file-based task tracking system within your repository to organize technical debt, feature requests, and code review feedback.

소개

The File-Based Todo Tracking skill implements a robust, git-friendly task management system using Markdown files and YAML frontmatter. It enables developers and AI agents to document findings, propose solutions, track dependencies, and maintain detailed work logs without leaving the codebase. This skill is ideal for projects that require persistent, version-controlled tracking of complex tasks, architectural decisions, and technical debt that exceeds the scope of simple inline comments.

주요 기능

Automated file naming conventions and YAML frontmatter generation
Inter-task dependency tracking to identify blockers and ready work
Structured todo lifecycle management from pending to complete
Comprehensive work log system for historical record and context sharing
0 GitHub stars
Integration with code reviews and automated triage workflows

사용 사례

Standardizing technical debt documentation and triage processes across a development team
Managing complex refactors and features that require multi-step execution and research
Converting code review feedback and findings into actionable, tracked work items

소개

주요 기능

Automated file naming conventions and YAML frontmatter generation
Inter-task dependency tracking to identify blockers and ready work
Structured todo lifecycle management from pending to complete
Comprehensive work log system for historical record and context sharing
0 GitHub stars
Integration with code reviews and automated triage workflows

사용 사례

Standardizing technical debt documentation and triage processes across a development team
Managing complex refactors and features that require multi-step execution and research
Converting code review feedback and findings into actionable, tracked work items