todo-triage

Triage pending todos by severity and category across local todo directories.

434|33|Updated Jul 27, 2025
One-click install
npx skills add https://github.com/udecode/kitcn --skill todo-triage-udecode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-triage
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/todo-triage
Command: npx skills add https://github.com/udecode/kitcn --skill todo-triage-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers systematically process pending todos by assessing severity and category, and deciding whether to approve, skip, or modify each item.

Core Features & Use Cases

  • Present each finding with severity, category, description, location, problem scenario, proposed solution, and effort estimate, and ask for a decision.
  • Handle decisions by updating file statuses (approve, skip, or modify) and record progress with a ready state and action notes.
  • Generate a final summary of approved and skipped items and prepare for the next steps like running /todo-resolve or committing changes.

Quick Start

Begin triaging pending todos by feeding the system the list from .context/compound-engineering/todos/ and start processing them one by one.

Frequently Asked Questions about todo-triage

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

FAQPage Schema
How do I triage pending todos in a codebase to decide what to approve or skip?

To triage pending todos, evaluate each item's severity, category, and impact to determine whether to approve, skip, or modify it. This interactive process standardizes dispositions across local todo directories by applying deterministic decisions based on those criteria.

What is the best way to prioritize engineering tasks based on severity and impact?

Prioritizing engineering tasks by severity and impact involves presenting each finding with its problem scenario and proposed solution, then making a deterministic decision. This method ensures reviewers systematically process pending todos by assessing effort estimates and category before updating file statuses.

How do I manage todo file statuses using frontmatter updates during code review?

Managing todo file statuses with frontmatter updates involves recording progress through ready and create actions. As you triage items, the system preserves issue details and applies deterministic decisions by directly modifying the frontmatter to reflect whether each item was approved, skipped, or modified.

Can I process legacy todos directories alongside local context paths for task prioritization?

Yes, you can process legacy todos directories alongside local .context/compound-engineering/todos/ paths. The triage workflow applies uniformly across both directory types to standardize every pending item's disposition and ensure consistent task-management practices.

What do I do after triaging pending todos and generating a final summary?

After triaging pending todos and generating a final summary of approved and skipped items, prepare for next steps like running /todo-resolve or committing changes. The summary distinguishes approved items ready for resolution from skipped ones, guiding subsequent engineering actions.