file-todos

Track file-based todos by storing them in a dedicated directory using YAML frontmatter. This approach automates status transitions, manages dependencies, and integrates with code review workflows to improve traceability.

File-based issue tracking uses the naming pattern {issue_id}-{status}-{priority}-{description}.md to organize and categorize todos, ensuring clear identification and streamlined triage during code reviews.

Yes, file-based todo management integrates directly with slash commands and code review workflows. This streamlines issue triage, tracks status transitions from pending to complete, and manages todo dependencies.

Set up structured repository todos by creating a SKILL.md with YAML frontmatter containing name and description. Use an optional template file to guide todo creation and define workflow templates for the directory.

Manage markdown todo dependencies using a structured, frontmatter-driven workflow. This method automates status transitions and tracks relationships between pending, ready, and complete todos for better collaboration.

File-based tracking operates entirely within the repository using markdown files and YAML frontmatter, eliminating the need for external issue tracking tools while maintaining traceability and structured organization.