file-todos

Create and manage file-based todos with YAML frontmatter and templates.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/8b-is/8b-is-mp --skill file-todos-8b-is
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/8b-is/8b-is-mp/tree/main/plugins/compound-engineering/skills/file-todos
Command: npx skills add https://github.com/8b-is/8b-is-mp --skill file-todos-8b-is

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill enables teams to manage code-review feedback, technical debt, and feature requests using a consistent file-based todo system stored in the todos/ directory. It reduces context switching and ensures traceable, auditable work items across reviews and planning.

Core Features & Use Cases

  • Todo lifecycle management: create, triage, assign status (pending → ready → complete) and track dependencies.
  • PR-comment to todo: convert succinct PR feedback into structured, versioned todos.
  • Documentation and workflows: template-based todos and slash-command integration align with code-review processes.

Quick Start

Review the existing todos directory and start by copying the template from assets/todo-template.md to a new path like todos/001-pending-p1-implement-feature.md, then fill in the required sections, set dependencies, and use /triage to move it forward.

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 as file-based todos?

You can track code-review feedback as file-based todos by copying a standardized markdown template with YAML frontmatter into a todos directory, then filling in the required sections and using slash-command workflows to triage status updates.

What is the best way to convert PR comments into structured technical debt items?

Converting PR comments into structured technical debt items involves applying a standardized template and YAML schema to create versioned todo files, enabling traceable lifecycle management from pending to complete states.

Can I manage todo dependencies and triage status using markdown files?

Yes, you can manage todo dependencies and triage status using markdown files by enforcing a YAML frontmatter schema that tracks lifecycle states and dependencies, supporting slash-command triage workflows.

Does this file-based todo workflow require any external dependencies?

No external dependencies are required to use this file-based todo workflow, as it relies entirely on markdown templates, YAML frontmatter enforcement, and an optional directory structure for scripts and references.

How do I start creating a code-review todo from a template?

To start creating a code-review todo, copy the provided markdown template from the assets directory into a new file path within your todos directory, then populate the required sections and set dependencies before triaging.