How does this skill handle task dependencies?

Tasks include a 'dependencies' field in their YAML frontmatter, allowing the skill to identify which items are blocked and which are ready to be worked on.

What is a file-based todo tracking system?

It is a method of managing project tasks using individual Markdown files stored directly in your repository, allowing for version-controlled task tracking alongside your code.

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

You should create a todo for tasks requiring more than 20 minutes of work, those needing research or approval, or items with dependencies on other work.

Can I use this for team collaboration?

Yes, because the todos are Markdown files in the repository, they can be committed, branched, and reviewed just like standard source code.

File-Based Todo Tracker

Name: File-Based Todo Tracker
Author: Activer007

byActiver007

Productivity & Workflow

Manages code review feedback, technical debt, and feature requests through a structured Markdown tracking system in your repository.

About

The File-Based Todo Tracker skill establishes a standardized workflow for managing project work items directly within a repository's file system. By using Markdown files with YAML frontmatter, it enables developers and AI agents to document findings, propose solutions, and track task lifecycles from triage to completion. This system is ideal for capturing complex technical debt, planning refactors, and maintaining detailed work logs that stay version-controlled alongside the source code, ensuring that project context is never lost in external tools.

Key Features

Structured Markdown templates with YAML frontmatter for consistent task documentation
Standardized file naming convention incorporating issue IDs, status, and priority
Integration with code review processes to convert findings into actionable todos
Chronological work logs for historical record-keeping and knowledge sharing
0 GitHub stars
Built-in dependency management to track blockers and unblocked work items

Use Cases

Capturing and triaging technical debt identified during code reviews or refactoring sessions
Maintaining a local, version-controlled project roadmap for solo or small-team development
Managing complex feature requests that require research, planning, and multiple sub-tasks

About

Key Features

Structured Markdown templates with YAML frontmatter for consistent task documentation
Standardized file naming convention incorporating issue IDs, status, and priority
Integration with code review processes to convert findings into actionable todos
Chronological work logs for historical record-keeping and knowledge sharing
0 GitHub stars
Built-in dependency management to track blockers and unblocked work items

Use Cases

Capturing and triaging technical debt identified during code reviews or refactoring sessions
Maintaining a local, version-controlled project roadmap for solo or small-team development
Managing complex feature requests that require research, planning, and multiple sub-tasks