file-todos

You can track code review feedback and technical debt by creating structured markdown files with YAML frontmatter inside a 'todos/' directory. This approach captures problem statements, findings, solutions, acceptance criteria, and work logs for each task item.

Managing task dependencies in a file-based workflow involves defining relationships between individual todo items within a 'todos/' directory. You can link pending tasks, conduct triage, and prioritize items based on their dependency chains to unblock downstream work.

Creating a todo item for a feature request or bug fix requires generating a markdown file in the 'todos/' directory. Each file uses YAML frontmatter to structure the entry, tracking its lifecycle from pending to ready to complete with detailed work logs.

Yes, file-based todo tracking integrates with slash commands and code review processes. The system uses markdown files with YAML frontmatter to capture code review feedback, allowing you to trigger todo creation and triage directly during your review workflow.

Triage and prioritization for technical debt tasks works by reviewing pending markdown todo files within the 'todos/' directory. You assign priorities and manage dependencies between items to determine which technical debt tasks are ready for implementation.