file-todos

Standardize file-based todo tracking with YAML frontmatter and Markdown templates.

Updated Oct 27, 2025
One-click install
npx skills add https://github.com/SomtoUgeh/dotfiles --skill file-todos-somtougeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/SomtoUgeh/dotfiles/tree/main/claude/skills/file-todos
Command: npx skills add https://github.com/SomtoUgeh/dotfiles --skill file-todos-somtougeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill provides a structured approach to managing file-based todos within the todos/ directory, enabling consistent creation, triage, lifecycle tracking, and integration with slash commands and code review workflows.

Core Features & Use Cases

  • Todo lifecycle management: create, triage, and progress items through pending, ready, and complete states.
  • Template-driven workflows: leverage a standardized Markdown template for new todos and work logs to ensure consistency.
  • Dependency and impact tracking: manage dependencies between todos and link related findings from code reviews or feedback.
  • Slash-command triggered actions: streamline creation and triage via slash commands during development workflows.
  • Code review integration: convert PR comments or findings into tracked work for visibility and accountability.

Quick Start

Start by duplicating the provided template and placing a new todo in the todos/ directory. For example, copy assets/todo-template.md to todos/005-pending-p2-new-feature.md, then edit the frontmatter and sections to reflect the issue and plan.

Frequently Asked Questions about file-todos

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

FAQPage Schema
How do I track file-based todos for code reviews?▼

File-based todos for code reviews are tracked using a standardized Markdown template within a todos/ directory. This enforces a YAML frontmatter schema to manage todo states, dependencies, and triage, ensuring visibility across code reviews.

What is the best way to convert PR comments into tracked work items?▼

Converting PR comments into tracked work items is handled by integrating file-based todo tracking directly into code review workflows. Findings are structured using a standardized Markdown template, linking related feedback and managing dependencies for accountability.

How do I create a new todo from a Markdown template?▼

To create a new todo, duplicate the provided Markdown template file and place it into the todos/ directory. You then edit the YAML frontmatter and sections to reflect the specific issue and execution plan.

Can I use slash commands to triage code work todos?▼

Slash commands can be used to trigger actions for creating and triaging file-based todos during development workflows. This streamlines todo lifecycle management, moving items through pending, ready, and complete states.

Does this todo management approach track dependencies between work items?▼

Dependency tracking between todos is supported natively. The YAML frontmatter schema allows you to manage dependencies between todos and link related findings from code reviews or feedback.

When do I need a standardized YAML frontmatter schema for todos?▼

A standardized YAML frontmatter schema for todos is needed when you require consistent creation, lifecycle tracking, and code review integration across a shared directory. It ensures uniform visibility and accountability for bug fixes and feature work.