What problem does it solve? Teams lose track of code review findings, technical debt, and feature requests scattered across PR comments and chat threads. This Skill provides a structured, file-based system in a todos/ directory where every work item is a markdown file with YAML frontmatter, making work visible, triageable, and traceable. ## Core Features & Use Cases - Todo Lifecycle Management: Create, triage, and complete todos following a pending → ready → complete status flow with sequential issue IDs and priority levels (p1/p2/p3). - Dependency Tracking: Declare blocking relationships between todos in YAML frontmatter and query them with grep commands to find unblocked work. - Structured Templates: Use the included todo-template.md with required sections (Problem Statement, Findings, Proposed Solutions, Acceptance Criteria, Work Log) for consistent documentation. - Use Case: After a code review surfaces 12 missing test scenarios, create a prioritized todo file with proposed solutions, triage it to ready status, track work sessions in the Work Log, and mark it complete once acceptance criteria pass. ## Quick Start Ask the agent to create a new todo in the todos directory for the performance issue you just found, using the template and assigning it priority p1.
