file-todos

Track todo dependencies by modeling each task as a markdown file in a todos/ directory with structured frontmatter. This approach supports creating, triaging, and prioritizing work items while linking related tasks within development workflows.

Manage file-based todos using structured markdown templates that capture problem statements, findings, and acceptance criteria. These files integrate with slash commands and code review processes to drive accountability and visibility across teams.

Yes, structured frontmatter is required to organize markdown todos. The system relies on this frontmatter alongside reference templates to standardize triage, dependency tracking, and workflow integration for each task file.

Slash-command based triage works by executing workflow steps that create, prioritize, and close markdown todo files. These commands operate on structured files in the todos/ directory to maintain consistent task lifecycle management.

Yes, you can use markdown todo files for dependency tracking. Each task is modeled as a file in the todos/ directory, enabling you to map dependencies, log work progress, and reference related discussions during development.

Avoid markdown-based todo workflows if your project requires real-time synchronization or heavy relational data linking beyond simple dependency tracking. This approach uses static files and is best suited for text-driven triage and code review integration.