todo-review

Validate TODO file format, freshness, and implementation readiness.

4|Updated Feb 9, 2021
One-click install
npx skills add https://github.com/breengles/poor-man-OS-setup --skill todo-review-breengles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-review
Source: https://github.com/breengles/poor-man-OS-setup/tree/main/.claude/skills/todo-review
Command: npx skills add https://github.com/breengles/poor-man-OS-setup --skill todo-review-breengles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted engineering time by validating a TODO file’s structure, dependencies, and readiness before implementation starts.

Core Features & Use Cases

  • Format compliance audit: Checks that the file contains a correct Priority Summary table, valid internal anchors, and no disallowed markup patterns.
  • Resolution order verification: Ensures the Suggested resolution order exists, is an appropriate bullet list, includes all pending items, and has rationales.
  • Freshness and item quality checks: Looks for signs items are stale by checking cited markers, spot-checking referenced behavior, and reviewing recent commit signals.
  • Output-focused triage: Produces PASS/WARN/FAIL verdicts with concrete evidence for anything blocking implementation.

Quick Start

Ask the skill to review your TODO file by running /todo-review todos/solver.md.

Frequently Asked Questions about todo-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a TODO file's structure and freshness before coding?

Validate a TODO file's structure and freshness by checking its format compliance, internal anchor integrity, and resolution order. This read-only review process identifies stale items and dependency inconsistencies to produce evidence-based PASS, WARN, or FAIL verdicts.

What is task triage for Markdown TODO files and how does it work?

Task triage for Markdown TODO files is a read-only review mechanism that audits priority summaries, dependency consistency, and resolution order rationales. It works by spot-checking referenced behaviors and recent commit signals to ensure implementation readiness without modifying the target file.

How do I check internal anchor integrity and format compliance in a TODO file?

Check internal anchor integrity and format compliance by enforcing structural Markdown requirements and verifying that disallowed markup patterns are absent. The review validates that a correct Priority Summary table exists alongside a complete Suggested resolution order bullet list.

Can I review TODO files automatically if I have multiple task areas?

You can review TODO files automatically across multiple task areas by relying on automatic selection of the most recently modified TODO under the todos/ directory. Alternatively, you can specify an explicit file path or use a named area-to-file mapping for single-area reviews.

Why does my TODO file fail a readiness check before starting implementation work?

Your TODO file fails a readiness check when it lacks a valid Priority Summary table, contains broken internal anchors, or has an incomplete Suggested resolution order missing rationales. Dependency inconsistencies and stale items flagged by recent commit signals also trigger FAIL verdicts.

Does the TODO review process modify my target Markdown file?

The TODO review process does not modify your target Markdown file. It operates as a strictly read-only review that generates PASS, WARN, or FAIL reports with concrete evidence for anything blocking implementation, ensuring your original task data remains untouched.