file-todos

Manage todo lifecycle in Markdown files with YAML frontmatter.

Updated Mar 12, 2026

Search Tags:#task management #code management #workflows #file-based #todo tracking

Ready to run

npx skills add https://github.com/GuitarAlchemist/ix --skill file-todos-guitaralchemist

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the management of file-based todo tracking systems, enabling efficient creation, triage, and completion of tasks within a codebase.

Core Features & Use Cases

Todo Creation: Generate new todos from findings or feedback, structured with a clear format.
Lifecycle Management: Facilitate the transition of todos from pending to ready and complete states.
Triaging: Triage pending items for approval, ensuring proper prioritization and dependencies are addressed.
Integration: Seamlessly integrate with code review processes and slash commands.
Use Case: Ideal for teams managing technical debt, feature requests, and work items within a code repository.

Quick Start

Create a new todo for a pending issue: create-todo "001-pending-p1-issue-fix.md"

Frequently Asked Questions about file-todos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage file-based todo tracking using Markdown and YAML frontmatter?▼

File-based todo tracking with Markdown and YAML frontmatter is managed by creating structured files for tasks, then triaging and transitioning them through pending, ready, and complete lifecycle states within your codebase.

What is the best way to create a new todo item from code review findings?▼

Creating a new todo from code review findings requires generating a Markdown file with a specific naming convention like `001-pending-p1-issue-fix.md` and populating it with YAML frontmatter to structure the task details and dependencies.

Do I need to know YAML to use a file-based task management workflow in my repository?▼

You need YAML knowledge to configure file naming and frontmatter properly within this file-based task management workflow, ensuring your technical debt and feature request items are correctly structured for triage and completion tracking.

How does triaging pending todos work in a file-based code management system?▼

Triaging pending todos in a file-based code management system involves reviewing Markdown task files, verifying dependencies are addressed, ensuring proper prioritization, and transitioning approved items into a ready state for implementation.

Can I integrate file-based todo tracking directly into my code review processes?▼

File-based todo tracking integrates seamlessly with code review processes and slash commands, allowing your team to generate work items from feedback and manage technical debt directly within the repository workflow.

When should I avoid using a file-based todo tracking system for code management?▼

You should avoid file-based todo tracking if your team requires a centralized database for task management rather than Markdown files, or if your workflow cannot accommodate YAML frontmatter configuration for task lifecycle states.