file-todos

File-based todos store work items as markdown files in a todos/ directory with YAML frontmatter defining status, priority, and dependencies. Each todo follows a standardized naming convention and lifecycle from pending to ready to complete, enabling teams to manage code reviews and task tracking in version control.

Yes. Define dependencies in todo frontmatter to establish blocking relationships. Todos remain pending until their prerequisite items reach completion, supporting triage workflows that enforce logical work sequencing.

The skill integrates with Claude Code workflows through slash commands and code review pipelines to auto-generate and triage todos from findings. This enables capturing work directly from review processes and maintaining structured tracking within development pipelines.

Use the included assets/todo-template.md template for all new todos. The template enforces consistent YAML frontmatter structure and markdown sections—Problem Statement, Findings, Proposed Solutions, Acceptance Criteria—ensuring uniformity across the workflow.

Yes. Each todo maintains a work log section to document actions, learnings, and decisions. This creates a continuous record of problem-solving within the todo lifecycle, supporting team knowledge transfer and audit trails.