file-todos

Manage file-based TODOs with YAML frontmatter in branch-scoped directories.

8|1|Updated Jan 4, 2026

Search Tags:#template #todo #triage #code-review #file-based #work-log #branch-work

Ready to run

npx skills add https://github.com/BonJarber/claude-config --skill file-todos-bonjarber

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/BonJarber/claude-config/tree/main/skills/file-todos
Command: npx skills add https://github.com/BonJarber/claude-config --skill file-todos-bonjarber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill provides a structured, file-based system to track, triage, and close code review feedback, debt, and feature work within a branch-scoped todos/ directory.

Core Features & Use Cases

Branch-scoped TODOs stored as markdown files under todos/<branch>/, enabling isolation of work per feature.
Lifecycle management for pending, ready, and complete statuses with triage and dependencies.
Seamless integration with /review, /address-feedback, and /plan-feature commands to convert feedback into tracked work.

Quick Start

Create a new feature branch, initialize a branch-specific todos/ directory, and add your first TODO markdown file following the naming convention.

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 feature work within a specific branch?▼

You can track code review feedback using a file-based TODO system stored under a branch-scoped todos/<branch>/ directory. Each TODO is a markdown file with YAML frontmatter, enabling structured lifecycle management for pending, ready, and complete tasks.

What is the best way to organize file-based TODOs for code triage and development work?▼

The best way to organize file-based TODOs is using markdown files with standardized naming schemes and YAML frontmatter. This structure supports templates for problems, findings, solutions, acceptance criteria, and work logs for comprehensive development tracking.

Can I manage TODO dependencies and triage statuses without external project management tools?▼

Yes, you can manage TODO dependencies and triage statuses directly within your repository. The system supports lifecycle management for pending, ready, and complete statuses, allowing you to triage and track code debt entirely through file-based markdown records.

How do I integrate TODO tracking with code review and feature planning commands?▼

TODO tracking integrates seamlessly with /review, /address-feedback, and /plan-feature commands. This integration converts code review feedback directly into tracked markdown work items within your branch-scoped todos directory.

Does branch-scoped TODO tracking work for isolating feature development work?▼

Branch-scoped TODO tracking works effectively for isolating feature development work by storing tasks under todos/<branch>/ directories. This ensures all code review feedback, debt, and feature work remains separated per branch.