file-todos

Manage file-based todo items in Markdown with YAML frontmatter.

5|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/marchatton/agent-skills --skill file-todos-marchatton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/00-utilities/file-todos
Command: npx skills add https://github.com/marchatton/agent-skills --skill file-todos-marchatton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill provides a structured system for managing tasks, feedback, and technical debt directly within markdown files, ensuring work is tracked, triaged, and completed efficiently.

Core Features & Use Cases

  • Todo Creation: Generate new todo items from findings or feedback with a standardized file structure.
  • Triage & Prioritization: Manage the lifecycle of todos from pending to ready and complete, including priority setting.
  • Dependency Tracking: Define and manage inter-todo dependencies to ensure work is unblocked.
  • Use Case: When a code review identifies a bug, create a pending todo file detailing the issue, proposed solutions, and acceptance criteria. This todo can then be triaged, prioritized, and tracked through to completion.

Quick Start

Create a new todo file for a critical bug fix with the description 'fix-login-bug'.

Frequently Asked Questions about file-todos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track technical debt and development tasks using markdown files?▼

You can track technical debt using markdown files with YAML frontmatter to store task details, proposed solutions, and acceptance criteria. This provides a structured system for managing feedback and development tasks directly in your repository.

What is the best way to manage todo dependencies for code review findings?▼

Managing todo dependencies involves defining inter-todo relationships within the markdown file structure to ensure work remains unblocked. This tracks the lifecycle from pending to ready and complete, preventing dependencies from halting progress.

How do I create a structured todo item from a bug report or feedback?▼

Creating a todo item involves generating a new markdown file with a standardized naming convention and structured sections. It captures the issue description, proposed solutions, and acceptance criteria for tracking the bug fix to completion.

Can I triage and prioritize file-based todos without a dedicated issue tracker?▼

Yes, you can triage and prioritize file-based todos by setting priority levels and managing their lifecycle states from pending to ready and complete. This structured markdown approach replaces dedicated issue trackers for lightweight tracking.

Does file-based task management work for tracking bugs found during code reviews?▼

File-based task management works for code review bugs by creating a pending todo file detailing the identified issue. The todo is then triaged, prioritized, and tracked through to completion using structured markdown sections.