file-todos

File-based todos automate converting PR findings and code review feedback into structured tracked work. Create a todo from review comments using the provided template, which captures the problem statement, findings, proposed solutions, and acceptance criteria in YAML frontmatter, then triage and track completion in your todos/ directory.

The Skill manages dependency tracking within the todos/ directory structure, allowing you to define relationships between work items and triage pending tasks based on their prerequisites. Dependencies are embedded in todo metadata, enabling you to visualize blocking work and sequence completion logically.

Todos progress through states: pending → ready → complete. Create todos from findings, log work and status updates in the Work Log section, manage dependencies to move items to ready state, and mark complete when acceptance criteria are met. The Skill provides workflows for each lifecycle stage.

Yes, file-based todos integrate with slash commands and code-review processes, enabling you to trigger todo creation and updates directly from pull request workflows. This reduces context switching by keeping feedback and tracked work linked to the code review conversation.

Todos require YAML frontmatter and structured sections: Problem Statement, Findings, Proposed Solutions, Recommended Action, Acceptance Criteria, and Work Log. This standardized format ensures consistency across your backlog and supports the triage, tracking, and completion workflows.

By capturing PR comments and findings directly as tracked work items with dependencies and status, file-based todos eliminate the need to switch between review tools and external trackers. Triage and dependency management keep high-priority work visible and ready, reducing context loss.