file-todos

Manage Markdown todo files with YAML frontmatter for lifecycle tracking.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/fro-bot/systematic --skill file-todos-fro-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/fro-bot/systematic/tree/main/components/file-todos
Command: npx skills add https://github.com/fro-bot/systematic --skill file-todos-fro-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The File-Based Todo system provides a structured way to capture, triage, and manage code-review feedback and work items stored as markdown files in the todos/ directory, enabling consistent lifecycle tracking from pending to complete.

Core Features & Use Cases

  • Markdown-based todos stored in a predictable file structure with YAML frontmatter for status, priority, and dependencies.
  • End-to-end workflow support: triage, dependency tracking, work logs, and completion, including templates for new todos.
  • Use Case: a team member converts PR comments into tracked todos, triages them, and follows through to completion with documented work logs.

Quick Start

Create a new pending todo for a small enhancement using the provided template and place it in the todos/ folder.

Frequently Asked Questions about file-todos

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

FAQPage Schema
How do I manage code review feedback as file-based markdown todos?

File-based markdown todos are managed by storing them in a predictable todos directory using YAML frontmatter. This enables consistent lifecycle tracking from pending to complete, capturing status, priority, dependencies, and structured work logs.

Can I track dependencies and priorities within a markdown todo workflow?

Tracking dependencies and priorities in a markdown todo workflow is done via YAML frontmatter. The system links related work items, triages them by priority, and documents progress through a structured work log within each todo file.

What is the best way to triage pending todos stored as markdown files?

Triaging pending todos stored as markdown files is best handled by a structured lifecycle system reading YAML frontmatter. It evaluates status and priority fields, links dependencies, and updates the work log to move items from triage to done.

Do I need a specific directory structure for file-based todo management?

A specific directory structure is required for file-based todo management. Todos must be stored as markdown files within a predictable todos directory, with support for an optional assets folder for supplementary files used during the workflow.

Does this todo template system support linking work items across development workflows?

This todo template system supports linking work items across development workflows by using YAML frontmatter to define dependencies between markdown files. Teams can connect related code review tasks and track their completion status together.