file-todos

Manage file-based todos with YAML frontmatter and status transitions.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/jovermier/claude-code-plugins-ip-labs --skill file-todos-jovermier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/jovermier/claude-code-plugins-ip-labs/tree/main/plugins/dev/skills/file-todos
Command: npx skills add https://github.com/jovermier/claude-code-plugins-ip-labs --skill file-todos-jovermier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The file-based todo system provides a persistent, trackable way to manage work items using Markdown files with YAML frontmatter, enabling clear ownership, dependency tracking, and historical context for team collaboration.

Core Features & Use Cases

  • Persistent Todo Storage: Create, update, and track todos as standardized frontmatter markdown files within the todos/ directory.
  • Dependency & Lifecycle Tracking: Manage status transitions (pending, ready, complete) and reference dependencies to ensure work flows smoothly.
  • Use Case: A team uses todos to coordinate feature work, track blockers, and maintain an auditable work log across sprints.

Quick Start

Create a new todo using the /todo create command and fill out the provided template 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 project tasks using markdown files with YAML frontmatter?

You can track project tasks using markdown files by placing them in a todos/ directory and using YAML frontmatter to represent statuses and dependencies. This provides a persistent, trackable way to manage work items and coordinate team collaboration.

How do I manage task dependencies in a file-based todo workflow?

Managing task dependencies in a file-based todo workflow involves referencing dependencies within the YAML frontmatter of your markdown files. This ensures work flows smoothly by tracking status transitions like pending, ready, and complete.

What is the best way to create file-based todos for software projects?

The best way to create file-based todos is using the /todo create command, which generates a standardized markdown template with YAML frontmatter. You fill out the template to start tracking work with clear ownership and historical context.

Can I track todo status transitions like pending and complete in markdown?

Yes, you can track todo status transitions like pending, ready, and complete in markdown. The system implements a frontmatter schema that supports lifecycle management to maintain an auditable work log across sprints.

Does this file-based todo system require a specific directory structure?

The file-based todo system requires a todos/ directory to store standardized markdown files. It uses YAML frontmatter within these files to represent tasks, statuses, and dependencies for persistent storage and tracking.

Why use markdown files with frontmatter for project task tracking instead of a database?

Using markdown files with frontmatter for task tracking provides a persistent, trackable format that enables clear ownership, dependency tracking, and historical context for team collaboration without needing a separate database.