file-todos

Manage development tasks and technical debt in Markdown files within a 'todos/' directory.

Updated May 2, 2026

Search Tags:#markdown #task management #development workflow #dependencies #issue tracking #todos

Ready to run

npx skills add https://github.com/iliaal/compound-engineering-plugin --skill file-todos-iliaal

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a robust system for managing development tasks, technical debt, and feedback directly within Markdown files, streamlining project tracking and ensuring nothing falls through the cracks.

Core Features & Use Cases

File-Based Todo Management: Create, triage, and track todos using a consistent Markdown file structure and naming convention.
Dependency Tracking: Define and visualize dependencies between different todo items.
Workflow Integration: Seamlessly integrates with code reviews, PR comments, and planning sessions to capture actionable items.
Use Case: When a code reviewer leaves a comment on a Pull Request that requires a code change, you can use this skill to convert that comment into a formal todo item with a priority and status, ensuring it gets addressed.

Quick Start

Create a new todo file for a critical bug fix by running the command to create a new todo.

Frequently Asked Questions about file-todos

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

FAQPage Schema

How do I track development tasks and technical debt using Markdown files?▼

You can track development tasks using Markdown files by creating items in a dedicated 'todos/' directory, assigning priorities (p1, p2, p3), and updating statuses like pending or complete to manage technical debt.

Can I convert PR comments into actionable todo items?▼

Yes, you can convert PR comments into todo items by capturing the code review feedback, creating a formal Markdown task file, and assigning it a priority and status to ensure the actionable item gets addressed.

How do I manage task dependencies in a file-based issue tracking system?▼

File-based issue tracking manages dependencies by assigning unique issue IDs to each Markdown todo file, allowing you to define and visualize relationships between different development tasks.

What is the best way to triage pending development tasks in Markdown?▼

Triage pending tasks in Markdown by reviewing files in the 'todos/' directory, updating their status to ready or complete, and adjusting priority levels (p1, p2, p3) based on current project needs.

Do I need any external tools to manage todos with Markdown files?▼

No external tools are required; the system operates entirely file-based using a consistent Markdown structure and naming convention within a designated 'todos/' directory to track tasks and technical debt.

When should I use a file-based Markdown todo system over other issue tracking methods?▼

Use a file-based Markdown todo system when you need to integrate task tracking directly within your code repository, manage technical debt locally, and capture code review feedback without external dependencies.