File Todos

A structured approach to tracking todos as markdown files with YAML frontmatter, living right in your codebase's todos/ directory. You'd reach for this when converting PR comments into actionable work items, managing technical debt, or tracking code review feedback through a pending to ready to complete lifecycle. The file naming convention and dependency tracking make it more organized than scattered TODO comments, though you're committing to maintaining another directory in your repo. Fits naturally into projects where your team already thinks in markdown and wants todo context close to the code without bolting on external tools.