file-todos

Manage file-based todos as markdown files with YAML frontmatter.

23|2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/marcusrbrown/systematic --skill file-todos-marcusrbrown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/marcusrbrown/systematic/tree/main/skills/file-todos
Command: npx skills add https://github.com/marcusrbrown/systematic --skill file-todos-marcusrbrown

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill provides a structured, file-based Todo system to track code-review feedback, technical debt, and work items as lightweight, auditable markdown files in the todos/ directory.

Core Features & Use Cases

  • File-based Todos: Create and manage todos as markdown files with YAML frontmatter, enabling lightweight, human-readable tracking.
  • Lifecycle & Triaging: Manage status transitions (pending → ready → complete) and dependencies, with examples for triage and planning.
  • Slash Command & Code-Review Integration: Integrates into collaboration workflows, turning findings from reviews into tracked work.

Quick Start

Initialize a new todo workflow by creating a template file in todos/ from the provided asset template and begin triaging findings.

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 in markdown files?

Code review feedback and technical debt are tracked by converting findings into structured markdown todo files with YAML frontmatter. These files are stored in the todos/ directory to provide lightweight, human-readable, and auditable tracking across team projects.

What is the best way to manage a file-based todo lifecycle for code work?

A file-based todo lifecycle is managed by applying status transitions to markdown files, moving items from pending to ready and finally complete. This workflow handles status mapping and dependencies directly within the todos/ directory structure.

Do I need external libraries to manage a markdown todo workflow with YAML frontmatter?

No external libraries are needed to manage this markdown todo workflow beyond standard markdown tooling. The system relies entirely on YAML frontmatter embedded in markdown files within the todos/ directory for lightweight tracking.

Can I integrate todo triaging into slash command and code review workflows?

Todo triaging integrates into slash command and code review workflows by turning review findings into tracked work items. Findings are structured as markdown files in the todos/ directory, enabling seamless collaboration.

How do I initialize a file-based todo tracking system for technical debt?

Initialize a file-based todo tracking system by creating a template file in the todos/ directory from an optional asset template. This establishes the workflow structure needed to begin triaging technical debt findings.

What are the limitations of using markdown files for code todo triage?

Using markdown files for code todo triage provides no built-in database querying or automated dependency resolution. Tracking relies entirely on manual YAML frontmatter updates and human-readable file management within the todos/ directory.