file-todos

File-based todos use Markdown files with YAML frontmatter stored in a todos/ directory, creating a searchable, consistent record of work items. Each todo enforces required fields like status, priority, issue_id, tags, and dependencies, replacing ad-hoc notes with an auditable workflow.

Yes. The Skill manages todo lifecycle from pending to ready to complete, with built-in support for dependencies and tags. You can triage pending items, update work logs, and link related todos to coordinate work across code reviews and technical debt.

Use slash commands and code-review workflow integration to surface work items directly from pull requests. The Skill accepts feedback and findings, converts them into todos using the standardized template, and stores them in the todos/ directory with proper frontmatter.

The Skill provides a shared template and standardized filename pattern for todos/ directory. Create a new todo by following the template, which automatically enforces required YAML frontmatter fields and ensures consistency across all documents.

Yes. File-based todos handle feature requests, technical debt, and code-review feedback in a single system. Tag and prioritize items by type, manage dependencies between work streams, and maintain a unified, searchable record of all work.

No. Todos are stored as Markdown files with YAML frontmatter in the todos/ directory, making them version-controllable, searchable by standard text tools, and auditable without external infrastructure.