When should I create a todo versus acting immediately?

The skill recommends creating a todo for tasks requiring more than 15-20 minutes of work, research, planning, or manager approval to ensure the work is properly tracked.

What makes this different from standard code comments?

Unlike simple TODO comments, this skill creates structured Markdown files that include problem statements, findings, proposed solutions, and acceptance criteria, making tasks searchable and manageable.

Is this system compatible with git?

Yes, because all todos are stored as files in a dedicated directory, they are version-controlled, allowing your team to track task history and changes alongside your code.

How are task dependencies handled?

Tasks use issue IDs in their YAML frontmatter to list dependencies. The skill can then check for blocked items or find all tasks that are currently ready for implementation.

File-Based Project Todos

Name: File-Based Project Todos
Author: Microck

byMicrock

•

Collaboration Tools

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

About

The File-Based Project Todos skill provides a disciplined framework for managing development tasks directly within your codebase. By utilizing Markdown files with YAML frontmatter, it allows Claude to create, triage, and track the lifecycle of work items without requiring external project management tools. This skill is ideal for teams who want to keep their task history, dependency maps, and work logs co-located with their source code, ensuring that technical debt and complex refactors are documented, prioritized, and executed with full context.

Key Features

Integrated triage workflows for approving and moving tasks through the lifecycle
Standardized naming convention for issue tracking and status visibility
Sophisticated dependency management to track blocked and unblocked work
81 GitHub stars
Detailed work log sections for historical documentation of findings and actions
YAML frontmatter for metadata, tagging, and priority levels

Use Cases

Documenting and prioritizing long-term technical debt and architectural refactors
Managing complex feature rollouts that involve multiple dependencies across files
Converting code review feedback and PR comments into trackable development tasks

About

Key Features

Integrated triage workflows for approving and moving tasks through the lifecycle
Standardized naming convention for issue tracking and status visibility
Sophisticated dependency management to track blocked and unblocked work
81 GitHub stars
Detailed work log sections for historical documentation of findings and actions
YAML frontmatter for metadata, tagging, and priority levels

Use Cases

Documenting and prioritizing long-term technical debt and architectural refactors
Managing complex feature rollouts that involve multiple dependencies across files
Converting code review feedback and PR comments into trackable development tasks