file-todos

Track code review feedback as file-based todos by creating standardized markdown files in a repository todos/ directory. Each file uses YAML frontmatter for status, priority, and dependencies, converting PR comments into auditable work items.

Dependency management for markdown todos works by declaring blockers in the YAML frontmatter dependencies field. Before starting work, the system checks for unblocked items to ensure downstream tasks are ready and prevent stalled technical debt resolution.

Yes, slash commands support interactive triage of pending work items during PR reviews. They enable moving items from pending to ready or complete, updating frontmatter, and renaming files to reflect status changes automatically.

Maintain an audit trail for completed technical debt items by recording chronological Work Log entries within the markdown todo. This explicit logging ensures all actions are auditable and provides clear references when committing completed work.

Yes, YAML frontmatter is required to manage repository todos and work logs. It enforces consistent metadata capture for status, priority, issue_id, tags, and dependencies, ensuring standardized lifecycle management and unblocking of downstream work.

Filename conventions for todo lifecycle management require using sequential issue IDs and renaming files to reflect status transitions. This standardization ensures reliable tracking from pending through ready to complete states across the codebase.