file-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.

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.

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.

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.

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.