todo-pick

Extract one pending TODO.md item for review and completion.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill todo-pick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-pick
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/todo-pick
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill todo-pick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces accumulating technical micro-debt by guiding you to pick and fix one TODO.md item at a time, keeping momentum without large context switches.

Core Features & Use Cases

  • Single-item TODO triage: Reads TODO.md from the project root, filters pending items, and lets you select exactly one to address next.
  • Classifier-aware correction flow: Adjusts the required interaction based on classifier type (file, feature, or free-form) before proposing changes.
  • Safe completion mechanics: Marks the chosen item as done after validation, with explicit irreversible removal confirmation via --remove and reversible skipping via --skip.

Quick Start

In your project root, run /anti-vibe-coding:todo-pick to select one pending TODO.md micro-debt item, propose a fix, and mark it as completed.

Frequently Asked Questions about todo-pick

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

FAQPage Schema
How do I manage accumulating technical debt in a TODO.md file?

To manage technical micro-debt, this Skill parses your root TODO.md file, filters pending items, and guides you to select exactly one item to review, repair, and mark as completed.

What is the best way to triage pending TODO items during short maintenance sessions?

The best way to triage pending TODO items during short maintenance sessions is to extract one micro-debt task at a time via numbered or random selection, keeping your context switching minimal.

How does classifier-aware prompting work for code maintenance tasks?

Classifier-aware prompting adjusts the required interaction flow based on the TODO item's type—such as file, feature, or free-form—before proposing any code changes or corrections.

Can I safely skip or permanently remove TODO entries without breaking my workflow?

Yes, you can safely skip TODO entries reversibly using the --skip flag, or permanently remove them with explicit irreversible confirmation via the --remove flag after validation.

Does this TODO triage tool work without external dependencies?

Yes, this TODO triage tool works entirely without external dependencies, requiring only a TODO.md file in your project root to parse and manage pending micro-debt items.

When should I use a single-item TODO workflow for technical debt?

You should use a single-item TODO workflow for technical debt between substantial feature work, during short maintenance sessions, or when plan execution adds out-of-scope items to prevent backlog buildup.