file-todos

Create standardized markdown todo files with YAML frontmatter from code review feedback.

9|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/sylvanding/omelette --skill file-todos-sylvanding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-todos
Source: https://github.com/sylvanding/omelette/tree/main/.claude/skills/file-todos
Command: npx skills add https://github.com/sylvanding/omelette --skill file-todos-sylvanding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill solves the problem of disorganized, lost, or untracked development work items including code review feedback, technical debt, and feature requests, which often fall through the cracks without a structured tracking system.

Core Features & Use Cases

  • Structured Todo Creation: Generate standardized markdown todo files with YAML frontmatter, problem statements, proposed solutions, and acceptance criteria from code review findings or work requests.
  • Lifecycle & Dependency Management: Track todo status (pending → ready → complete), map task dependencies to prioritize unblocked work, and triage pending items for approval.
  • Workflow Integration: Syncs with code review, PR comment processing, and sprint planning processes to turn ad-hoc feedback into tracked, actionable work.
  • Use Case: A development team receives 15 code review comments across 3 pull requests; use this Skill to convert each comment into a tracked todo, triage pending items for the next sprint, map dependencies between related tasks, and log progress as work is completed.

Quick Start

Use the file-todos skill to create a new p1 priority todo for the N+1 query issue found in the recent user service code review, with a dependency on the pending database migration todo.

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 as structured todos?

You can track code review feedback and technical debt by converting pull request comments into standardized markdown todo files with YAML frontmatter, problem statements, proposed solutions, and acceptance criteria.

How do I manage development todo dependencies and lifecycle statuses?

Manage development todo dependencies by mapping task relationships to prioritize unblocked work, while tracking lifecycle statuses from pending to ready to complete for triage and approval.

Can I use file-based todos for sprint planning and work progress tracking?

Yes, file-based todos support sprint planning by triaging pending items for the next sprint and logging work progress as development tasks are completed across your workflow.

What is the best way to organize development work items with version-controllable task management?

The best way to organize development work is using a file-based system that provides persistent, version-controllable task management with status lifecycle controls and integration with existing development tooling.

Does this file-based todo system work with existing development workflows and PR comments?

Yes, the file-based todo system syncs with code review, PR comment processing, and sprint planning processes to turn ad-hoc feedback into tracked, actionable work items.

When should I use file-based todos over other task management approaches for software engineering?

Use file-based todos when you need persistent, version-controllable task management for software engineering workflows, ensuring code review findings and technical debt do not fall through the cracks.