skills.rest
CristoVentures
CristoVenturesOFFICIAL
Explore all skills by this author →
GitHub

file-todos

Create and manage markdown todos with YAML frontmatter in the todos/ directory.

2|Updated Apr 14, 2026
Search Tags:#workflow#markdown#todo#code-review#project-management
One-click install
npx skills add https://github.com/CristoVentures/LocalCents --skill file-todos-cristoventures
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/CristoVentures/LocalCents/tree/main/.agent/skills/file-todos
Command: npx skills add https://github.com/CristoVentures/LocalCents --skill file-todos-cristoventures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill provides structured workflows for managing the file-based todo tracking system in the todos/ directory, enabling consistent creation, status management, dependency tracking, triage, and integration with slash commands and code review processes.

Core Features & Use Cases

  • Todo files follow a naming convention: {issue_id}-{status}-{priority}-{description}.md to organize work items clearly.
  • Lifecycle support: pending → ready → complete, with triage and dependency tracking to coordinate work.
  • Triaging and work logging: convert findings into todos, update status, and log progress and decisions.
  • Integration with development workflows: tie todo actions to code reviews, PR comments, and planning discussions for better traceability.

Quick Start

Create a new todo in the todos/ directory using the naming convention and fill in the required sections.

Frequently Asked Questions about file-todos

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

FAQPage Schema
How do I track markdown todos for code review findings and technical debt?▼

To track markdown todos for code reviews, you create structured files in the todos/ directory using a YAML frontmatter schema to capture status, priority, issue_id, tags, and dependencies for each work item.

What is the best way to manage feature request status and dependencies in markdown files?▼

The best way to manage feature request status in markdown is enforcing a structured YAML frontmatter schema and a naming convention to track the lifecycle from pending to ready to complete.

How does file-based todo tracking integrate with project management workflows?▼

File-based todo tracking integrates with project management workflows by tying todo actions to code reviews, PR comments, and planning discussions, providing clear traceability for triage and progress logging.

Can I use markdown todo files to coordinate work items requiring dependency tracking?▼

Yes, you can coordinate work items requiring dependency tracking by defining relationships in the YAML frontmatter schema of each markdown todo file to ensure correct execution order.

What naming convention should I follow when creating a markdown todo for triage?▼

When creating a markdown todo for triage, you should follow the {issue_id}-{status}-{priority}-{description}.md naming convention to organize work items clearly inside the todos/ directory.

Do I need a specific tool to enforce the YAML frontmatter schema for markdown todos?▼

No specific external tool is required; the skill itself prescribes the structured template and enforces the YAML frontmatter schema to maintain consistency across your file-based todo tracking system.

Related Skills

Explore More Software Engineering Skills→
fro-botfro-bot

file-todos

Manage Markdown todo files with YAML frontmatter for lifecycle tracking.

Community
Advanced
zeketxzeketx

file-todos

Manage file-based todos with YAML frontmatter and Markdown files.

Community
Intermediate
iliaaliliaal
30

ia-file-todos

Create and manage Markdown todo files under the todos/ directory.

Community
Intermediate
hackefellerhackefeller
1

file-todos

Manage file-based todos with markdown and YAML frontmatter.

Official
Intermediate