file-todos

Manage file-based todos with YAML frontmatter and dependency tracking.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill addresses the challenge of scattered, inconsistent todo tracking across code projects by introducing a standardized, file-based system in the todos/ directory. It enables teams to create, classify, triage, track dependencies, and coordinate work items using plain Markdown files with YAML frontmatter.

Core Features & Use Cases

  • Todo lifecycle management: create new todos, triage pending items, move to ready, and mark as complete.
  • Dependency tracking: declare blockers and blocks for coordinated planning.
  • Template-driven work: use a consistent assets/todo-template.md to ensure uniform structure.
  • Slash-command and code-review integration: surface todo actions within development workflows and PR discussions.
  • Use Case: converting a noisy code review comment into a tracked todo for later follow-up and progress updates.

Quick Start

Use the skill's workflow to kick off a new todo:

  • Copy the template into the todos/ directory: cp assets/todo-template.md todos/001-pending-p2-new-feature.md
  • Edit the YAML frontmatter and the required sections (Problem Statement, Findings, Proposed Solutions, Acceptance Criteria, Work Log)
  • Start triage with a pending item and, once approved, rename to ready and finally to complete as work progresses
  • Add Work Log entries after each session to document actions, learnings, and results

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 in a code project directory?

To track file-based todos, use a standardized todos/ directory containing Markdown files with YAML frontmatter. This enforces consistent structure for issue tracking, dependency mapping, and triage workflows during code reviews and feature planning.

What is the best way to triage code review comments into actionable work items?

Triage code review comments by converting them into tracked Markdown files within a todos/ directory. Use a standardized template to classify pending items, declare blockers, and update status to ready or complete as work progresses.

How do I manage todo dependencies and blockers for feature planning?

Manage todo dependencies by declaring blockers and blocks directly in the YAML frontmatter of your todo files. This coordinates feature planning by linking pending work items and tracking their resolution status through the lifecycle.

Does file-based todo management require a specific template structure?

File-based todo management requires copying a standardized todo template into your project. This enforces a consistent structure with YAML frontmatter and required sections like Problem Statement, Findings, Proposed Solutions, Acceptance Criteria, and Work Log.

Can I integrate todo triage workflows directly into development cycles?

Yes, todo triage workflows integrate directly into development cycles through slash-command and code-review actions. This surfaces todo creation and status updates within PR discussions and maintenance workflows.

How do I document progress updates for tracked project todos?

Document progress updates by adding Work Log entries to your todo Markdown files after each session. This records actions, learnings, and results while the todo moves from pending to ready and finally to complete.