Can I manage task dependencies with this skill?

Yes, the skill tracks dependencies using unique issue IDs in the YAML frontmatter, allowing you to identify blockers and ensure tasks are completed in the correct logical order.

How do I update progress on a specific task?

You can use the 'Work Log' section within each todo file to record chronological entries, including actions taken, commands run, and key learnings discovered during execution.

What is the purpose of the 'pending' status?

The pending status is for items that need triage. It allows you to capture ideas or findings immediately without cluttering your active task list until they are reviewed and approved.

How does this differ from standard code TODO comments?

Unlike simple code comments, this skill uses structured markdown files with metadata, allowing for status tracking, priority levels, dependency mapping, and detailed work logs that persist independently of specific lines of code.

File-Based Todo Manager

Name: File-Based Todo Manager
Author: Activer007

byActiver007

Collaboration Tools

Manages project tasks and technical debt using a structured markdown-based tracking system within your repository.

About

The File-Based Todo Manager provides a robust framework for tracking code review feedback, technical debt, and feature requests directly in your codebase. By utilizing markdown files with YAML frontmatter in a dedicated directory, it enables clear task lifecycles (pending, ready, complete), priority levels, and complex dependency management. This skill is ideal for developers who want to maintain project momentum and historical context without leaving their terminal or IDE, ensuring that every finding is documented, triaged, and executed with a detailed work log.

Key Features

Comprehensive work logs for recording investigations, learnings, and actions
Automated file naming conventions using unique issue IDs and status indicators
Integrated triage workflows to move items from pending to approved status
0 GitHub stars
Standardized Markdown templates with YAML frontmatter for consistent task tracking
Advanced dependency management to track and verify blockers between tasks

Use Cases

Documenting and prioritizing technical debt that requires research and planning
Managing multi-step feature implementations with internal task dependencies
Converting complex code review findings into actionable, tracked work items

About

Key Features

Comprehensive work logs for recording investigations, learnings, and actions
Automated file naming conventions using unique issue IDs and status indicators
Integrated triage workflows to move items from pending to approved status
0 GitHub stars
Standardized Markdown templates with YAML frontmatter for consistent task tracking
Advanced dependency management to track and verify blockers between tasks

Use Cases

Documenting and prioritizing technical debt that requires research and planning
Managing multi-step feature implementations with internal task dependencies
Converting complex code review findings into actionable, tracked work items