file-todos

Organizes engineering findings and feedback into a file-based todo system with dependency tracking and lifecycle management.

50|2|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/roberto-mello/beads-compound-plugin --skill file-todos-roberto-mello
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/roberto-mello/beads-compound-plugin/tree/main/plugins/beads-compound/gemini/skills/file-todos
Command: npx skills add https://github.com/roberto-mello/beads-compound-plugin --skill file-todos-roberto-mello

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill helps engineering teams convert scattered findings, code review notes, and feedback into a centralized, trackable set of todos stored as markdown files.

Core Features & Use Cases

  • Centralized todo creation from findings and feedback
  • Lifecycle management (pending → ready → complete) with dependency tracking
  • Lightweight integration with slash commands and code-review workflows

Quick Start

Create a new todo using the template, then fill in problem, findings, proposed solutions, and acceptance criteria.

Frequently Asked Questions about file-todos

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

FAQPage Schema
How do I convert code review findings into trackable markdown todos?▼

Track code review findings by creating markdown files using a reusable template with a frontmatter-driven schema. This organizes scattered feedback into a durable knowledge surface by documenting problems, findings, proposed solutions, and acceptance criteria in one centralized location.

What is the best way to manage todo dependencies for engineering projects?▼

Manage todo dependencies by applying a lifecycle workflow that moves items from pending to ready to complete. This file-based system tracks dependencies and logs work to maintain accountability across engineering projects and code reviews.

Can I use a markdown todo system with slash commands for code review workflows?▼

Yes, you can integrate this markdown todo system with slash commands and code review workflows. It applies a lightweight frontmatter-driven schema to create and triage todos, enabling seamless workflow integration for both human reviewers and automated agents.

How does a frontmatter-driven schema improve engineering todo triage?▼

A frontmatter-driven schema improves engineering todo triage by enforcing a lightweight, structured format for markdown files. This standardizes logging work, managing dependencies, and tracking lifecycle states from pending to complete for humans and agents.

Do I need external dependencies to maintain a file-based todo logging system?▼

No external dependencies are required to maintain this file-based todo logging system. It operates independently using markdown files, a reusable template workflow, and a frontmatter-driven schema to create a durable knowledge surface for engineering teams.