file-todos

Organize code review feedback into markdown todos with YAML frontmatter.

3|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/roach88/compound-engineering --skill file-todos-roach88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/roach88/compound-engineering/tree/main/skills/file-todos
Command: npx skills add https://github.com/roach88/compound-engineering --skill file-todos-roach88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The todos/ directory contains a file-based tracking system for managing code review feedback, technical debt, feature requests, and work items. Each todo is a markdown file with YAML frontmatter and structured sections.

This skill should be used when:

  • Creating new todos from findings or feedback
  • Managing todo lifecycle (pending → ready → complete)
  • Triaging pending items for approval
  • Checking or managing dependencies
  • Converting PR comments or code findings into tracked work
  • Updating work logs during todo execution

Core Features & Use Cases

  • File-based tracking system for todos stored as markdown files with frontmatter
  • Lifecycle management: pending, ready, complete
  • Dependency tracking and triage workflows
  • Integration with slash commands and code review processes
  • Reusable templates via assets/todo-template.md for new todos

Quick Start

Create a new todo by copying assets/todo-template.md to todos/{NEXT_ID}-pending-{priority}-{description}.md and filling in the required sections.

Frequently Asked Questions about file-todos

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

FAQPage Schema
How do I convert PR review comments into tracked todos?

Converting code review notes into tracked todos involves creating a markdown file from a reusable template, populating YAML frontmatter, and organizing findings into structured sections for auditable work logs.

What is a file-based todo system for code review triage?

A file-based todo system uses markdown files with YAML frontmatter to manage code review feedback and technical debt. It enforces structured documentation and supports lifecycle stages like pending, ready, and complete.

How do I manage todo lifecycle and dependencies across projects?

Manage todo lifecycle by moving files through pending, ready, and complete stages. The system supports dependency tracking and triage workflows to manage work items across multiple projects.

Does this todo tracking approach require external dependencies?

No external dependencies are required. The system relies on portable markdown files with YAML frontmatter and structured sections, using a provided template to ensure consistent documentation.

What's the best way to log work during todo execution?

The best way to log work is by updating the structured sections within the markdown todo file. This enforces a YAML frontmatter schema to maintain auditable work logs throughout the execution phase.

How do I triage pending code review items?

Triage pending code review items by evaluating the markdown files in the todos directory. The file-based system supports triage workflows to approve and transition items from pending to ready.