file-todos

Manage file-based todo tracking with markdown and YAML frontmatter.

Updated Aug 23, 2026

Search Tags:#code review #task management #workflow automation #technical debt #issue tracking #todos

Ready to run

npx skills add https://github.com/greatxrider/nomanuAI --skill file-todos-greatxrider

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/greatxrider/nomanuAI/tree/main/.claude/plugins/compound-engineering/2.31.1/skills/file-todos
Command: npx skills add https://github.com/greatxrider/nomanuAI --skill file-todos-greatxrider

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill streamlines the management of code review feedback, technical debt, and feature requests by providing a structured, file-based system for tracking work items.

Core Features & Use Cases

Todo Creation: Easily create new todo items from findings or feedback, complete with detailed problem statements, findings, and proposed solutions.
Lifecycle Management: Manage the status of todos from pending to ready to complete, ensuring clear visibility and progress.
Dependency Tracking: Define and manage dependencies between todos to ensure work is prioritized and executed in the correct order.
Use Case: When a code review uncovers a piece of technical debt, you can use this skill to create a new pending todo, assign it a priority, and link it to any related issues, ensuring it's triaged and addressed systematically.

Quick Start

Use the file-todos skill to create a new pending todo for fixing the n-plus-1 query issue.

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 and technical debt using file-based todos?▼

File-based todos track code review feedback and technical debt by using markdown files with YAML frontmatter to represent work items. You create a pending todo, assign a priority, and link related issues to triage findings systematically within a designated directory.

What is the best way to manage dependencies between technical debt items in a local workflow?▼

Managing dependencies between technical debt items requires defining relationships within structured todo files. This ensures work is prioritized and executed in the correct order by tracking lifecycle statuses from pending to ready to complete across linked markdown files.

How do I create a structured todo for a feature request from code findings?▼

To create a structured todo for feature requests, generate a markdown file with YAML frontmatter in your tracking directory. Include detailed problem statements, findings, and proposed solutions to document the work item lifecycle from pending to complete.

Can I integrate file-based todo tracking directly into my development process?▼

Yes, file-based todo tracking integrates with development processes by managing item statuses and dependencies locally. The markdown-based system facilitates creating, triaging, and updating todos alongside code changes without requiring external issue tracking databases.

Do I need any external issue tracking databases to manage code tasks with markdown files?▼

No external issue tracking databases are needed. Code tasks are managed entirely through markdown files with YAML frontmatter, providing a structured representation for tracking technical debt, feature requests, and code review feedback locally.