file-todos

Name: file-todos
Availability: InStock
Author: merlyn-huntress

Manage file-based todos with markdown and YAML frontmatter.

Updated Feb 26, 2026

Search Tags:#project management #code review #markdown #task management #technical debt #todo

Ready to run

npx skills add https://github.com/merlyn-huntress/compound-engineering-plugin-no-mcp --skill file-todos-merlyn-huntress

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/merlyn-huntress/compound-engineering-plugin-no-mcp/tree/main/plugins/compound-engineering/skills/file-todos
Command: npx skills add https://github.com/merlyn-huntress/compound-engineering-plugin-no-mcp --skill file-todos-merlyn-huntress

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill provides a structured, file-based system for managing project todos, code review feedback, technical debt, and feature requests, ensuring nothing falls through the cracks.

Core Features & Use Cases

Todo Creation: Easily create new todo items from findings or feedback using a standardized markdown template.
Lifecycle Management: Track todos through pending, ready, and complete statuses.
Dependency Tracking: Define and manage dependencies between todo items.
Triage & Prioritization: Facilitate the review and prioritization of pending tasks.
Work Logging: Maintain a detailed chronological log of actions and learnings for each todo.
Integration: Seamlessly integrates with code review and PR comment workflows.

Quick Start

Use the file-todos skill to create a new todo for fixing the n-plus-1 query issue.

Frequently Asked Questions about file-todos

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

FAQPage Schema

How do I track code review feedback and technical debt using markdown files?▼

Markdown files with YAML frontmatter track code review feedback and technical debt by structuring todo items with statuses, dependencies, and chronological work logs. This file-based system captures findings directly from development workflows to prevent issues from falling through the cracks.

What's the best way to manage pending project todos and prioritize them for development?▼

Managing pending project todos involves using a structured markdown template with YAML frontmatter to define statuses like pending, ready, and complete. Triage features facilitate reviewing and prioritizing pending tasks, while dependency tracking maps relationships between todo items.

Can I integrate task management into my code review and PR comment workflows?▼

Task management integrates into code review and PR comment workflows using slash commands to create new todo items from findings or feedback. This connects development workflows directly to the file-based tracking system, capturing feedback as structured markdown items.

How does dependency tracking work for feature requests in a markdown todo system?▼

Dependency tracking for feature requests works by defining and managing relationships between todo items within individual markdown files. Each todo uses YAML frontmatter to map dependencies, allowing developers to visualize task order and unblock ready items.

What is a file-based todo tracking system and when do I need it for software engineering?▼

A file-based todo tracking system is a structured markdown approach for managing project todos, code review feedback, and feature requests without a database. You need it when ensuring technical debt and feedback are captured in development workflows without items falling through the cracks.

Does this markdown task management approach support detailed work logging for technical debt?▼

This markdown task management approach supports detailed work logging by maintaining a chronological log of actions and learnings for each todo item. Technical debt entries capture historical context within the file, tracking status transitions from pending to complete.