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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly inventory and organize scattered TODOs, FIXMEs, and improvement ideas into a clear tracking system so you can start tackling work without hunting through the repo.

Core Features & Use Cases

  • Project-wide TODO discovery: Scans the repository for TODO/FIXME/HACK/XXX markers across files, plus related documentation and contribution artifacts.
  • Area-based organization: Groups items into semantic areas that match the project’s structure (e.g., solver/api/ui/cli/tests/docs/infra).
  • Priority and status seeding: Creates one todos/<area>.md per area with a priority summary table (P0/P1/P2) and initializes each item as Pending.
  • Resolution guidance: Adds a recommended tackling order based on dependencies and prerequisites, enabling faster planning.

Quick Start

Use todo-init to scan the repository and generate initial todos/<area>.md files with prioritized, area-grouped TODO items.

Frequently Asked Questions about todo-init

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

FAQPage Schema
How do I organize scattered TODO and FIXME comments across a codebase?

Organizing scattered TODO and FIXME comments involves scanning source files and documentation to discover markers, then grouping them semantically into project areas. This creates structured tracking files with prioritized summaries for actionable maintenance.

What is the best way to track technical debt in a software repository?

Tracking technical debt requires discovering TODO-style markers across the repository and grouping them into area-based tracking files. This approach seeds priority levels and statuses, providing a structured output for resolving pending items.

How do I generate priority summaries for existing project TODOs?

Generating priority summaries for project TODOs involves scanning the repository for improvement markers and initializing area-specific markdown files. Each file includes a three-column priority table categorizing items by P0, P1, or P2 urgency.

Can I automatically group codebase audit items by project area?

Codebase audit items can be automatically grouped by project area by scanning the repository and matching discovered TODO markers to semantic structural areas. This generates dedicated tracking files for each identified project area.

Does project maintenance scanning work with existing documentation files?

Project maintenance scanning works with existing documentation files by discovering TODO-style markers and contribution artifacts alongside source code. It incorporates these findings into the area-based tracking system for comprehensive prioritization.

How do I establish a recommended resolution order for pending TODO items?

Establishing a resolution order for pending TODO items requires analyzing dependencies and prerequisites across discovered markers. The generated tracking files include a recommended tackling order to enable faster project planning and maintenance.