file-todos

Manage file-based todos with YAML frontmatter and lifecycle states.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/isndotbiz/ged --skill file-todos-isndotbiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/isndotbiz/ged/tree/main/.claude/skills/file-todos
Command: npx skills add https://github.com/isndotbiz/ged --skill file-todos-isndotbiz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The todos/ directory provides a lightweight, file-based tracking system for capturing code review feedback, technical debt, feature requests, and work items. Each todo is a Markdown file with YAML frontmatter and clearly structured sections, enabling offline triage, lifecycle management, and easy sharing within a repository.

Core Features & Use Cases

  • File-based todos with YAML frontmatter to define status, priority, dependencies, and tags.
  • Lifecycle management from pending to ready to complete, plus triage workflows and dependency tracking.
  • Templates and conventions for creating new todos and integrating with slash commands and code review processes.

Quick Start

Copy the assets/todo-template.md into a new todos/{NEXT_ID}-pending-<priority>-<description>.md and fill the required sections to start tracking work.

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 a repository?

File-based todo tracking uses Markdown files with YAML frontmatter to capture code review feedback and technical debt. Each file defines status, priority, dependencies, and tags, enabling offline triage and lifecycle management within your repository.

How do I create a new todo for code review items?

To create a new todo, copy the provided Markdown template into a todos directory using the naming convention for pending status, priority, and description. Fill out the required YAML frontmatter and structured sections to start tracking work.

What is the lifecycle workflow for file-based todos?

The file-based todo lifecycle progresses from pending to ready to complete. This workflow supports triage operations, dependency tracking across projects, and status updates defined in the YAML frontmatter of each Markdown file.

Can I manage dependencies across multiple projects with markdown todos?

Yes, the file-based todo system supports dependency handling across projects. You can define and track dependencies within the YAML frontmatter of each todo file to manage work items spanning different areas of your repository.

What is the best way to organize technical debt tracking in a codebase?

Using a file-based markdown todo system provides a lightweight approach to organizing technical debt. It enforces consistent templates with YAML frontmatter for priorities and statuses, enabling easy sharing and offline triage directly within the codebase.