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

You should create a todo if the task requires more than 20 minutes of work, involves research, has dependencies on other items, or needs explicit triage and prioritization.

Are these todos version-controlled?

Absolutely. Since todos are stored as markdown files in the /todos directory, they are committed to your repository, providing a versioned history of project tasks and decisions.

How does this differ from a database-backed Todo model?

This skill manages a file-based system for internal project and developer tracking within the repository. It is intended for managing the development process itself, rather than user-facing application data.

Can I track dependencies between different tasks?

Yes, the skill uses YAML frontmatter to define issue IDs that block a specific task, allowing you to easily identify what work is ready to start and what is blocked.

Does it support work logs?

Yes, it includes a structured Work Log section for each todo to record specific actions, commands executed, and learnings discovered during the execution of a task.

File-Based Todo Manager

Name: File-Based Todo Manager
Author: Microck

byMicrock

•

Productividad y Flujo de Trabajo

Manages a structured, file-based task tracking system directly within your repository using Markdown and YAML frontmatter.

Acerca de

The File-Based Todo Manager is a specialized Claude Code skill designed to streamline technical debt management and feature tracking through a repository-centric workflow. By utilizing markdown files in a dedicated directory, it enables developers and AI agents to create, triage, and execute complex tasks with full traceability. The skill automates the lifecycle of work items—from initial finding and dependency mapping to comprehensive work logging and completion—ensuring that project context and decisions are preserved alongside the codebase for better team alignment and historical record-keeping.

Características Principales

Detailed chronological work logging for documenting investigations and findings
Advanced dependency tracking to manage blockers and work sequences
Standardized markdown todo creation with YAML frontmatter and structured sections
Automated triage workflow for approving, deferring, and prioritizing pending tasks
Integration with PR reviews and code findings to convert feedback into tracked work
81 GitHub stars

Casos de Uso

Managing long-running refactors or technical debt that requires research and multiple steps
Maintaining a persistent audit trail of development decisions and progress within the repository
Converting complex code review feedback into actionable, version-controlled work items

Acerca de

Características Principales

Detailed chronological work logging for documenting investigations and findings
Advanced dependency tracking to manage blockers and work sequences
Standardized markdown todo creation with YAML frontmatter and structured sections
Automated triage workflow for approving, deferring, and prioritizing pending tasks
Integration with PR reviews and code findings to convert feedback into tracked work
81 GitHub stars

Casos de Uso

Managing long-running refactors or technical debt that requires research and multiple steps
Maintaining a persistent audit trail of development decisions and progress within the repository
Converting complex code review feedback into actionable, version-controlled work items