file-todos

Organize and track code-related todos with YAML frontmatter in the todos/ directory.

Updated Mar 22, 2026

Search Tags:#workflow #template #markdown #todo #triage #code-review #dependency

Ready to run

npx skills add https://github.com/drhazemibclc/plate --skill file-todos-drhazemibclc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/drhazemibclc/plate/tree/main/.codex/skills/file-todos
Command: npx skills add https://github.com/drhazemibclc/plate --skill file-todos-drhazemibclc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The File-Based Todo Tracking Skill provides a structured, markdown-based system to create, triage, and manage todos within the todos/ directory, converting feedback and findings into trackable work items that can be linked to code reviews and slash commands.

Core Features & Use Cases

Todo files in todos/ use YAML frontmatter for tracking status, priority, dependencies; enables lifecycle from pending to complete.
Standardized naming convention for issue tracking and easy filtering and reporting.
Triage, dependency tracking, work logs, and recommended actions to plan work before coding.
Integration with slash commands and code review processes to surface tasks directly from feedback.

Quick Start

Copy the provided template, fill in the required sections, and begin tracking a new todo in the todos/ directory.

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 tasks using markdown files?▼

Track code review tasks using markdown files by applying YAML frontmatter for status, priority, and dependencies, placing them in a todos/ directory. This enables lifecycle management from pending to complete and integrates feedback into trackable work items linked to code reviews.

What is the best way to organize code work with file-based todos?▼

Organize code work with file-based todos by copying a standardized template into the todos/ directory. This template specifies required sections for triage, work logs, and recommended actions, allowing you to plan work and track dependencies before coding begins.

Can I use YAML frontmatter to manage todo dependencies and lifecycle?▼

Yes, YAML frontmatter manages todo dependencies and lifecycle by defining tracking fields for status, priority, and dependencies. This enables filtering, reporting, and transitioning work items from pending to complete within the todos/ directory.

How do I convert code review feedback into trackable markdown todos?▼

Convert code review feedback into trackable markdown todos by using a standardized naming convention and template. This process surfaces tasks directly from feedback, integrating them with slash commands to create structured work items in the todos/ directory.

Do I need a specific template to create file-based todos for triage?▼

Yes, you need a specific template to create file-based todos for triage. The system uses an assets/template to define required sections and YAML frontmatter schema, ensuring consistency for dependency tracking, work logs, and recommended actions across all todos.

When should I not use a markdown todo system for code work?▼

You should not use a markdown todo system for code work if your project requires dynamic real-time issue syncing rather than file-based tracking, or if your workflow lacks integration points for slash commands and code review processes to surface feedback.