skills.rest
mukles
muklesCOMMUNITY
Explore all skills by this author →
Website𝕏@mukles_devGitHub

todo-triage

Triage pending todos from local directories for approve, skip, or modify decisions.

Updated Sep 16, 2025
Search Tags:#workflow#prioritization#engineering#todo#triage#code-review
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill todo-triage-mukles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: todo-triage
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/todo-triage
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill todo-triage-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing and prioritizing a backlog of pending todos can be tedious and error-prone. This skill provides an interactive triage workflow to review each item, categorize it by severity and project area, and decide whether to approve, skip, or request modifications.

Core Features & Use Cases

  • Interactive review: Presents each finding with severity, category, description, location, problem scenario, proposed solution, and effort estimate.
  • Decision workflow: Allows three outcomes per item: approve (move to ready), skip (delete), or modify (re-prompt for adjustments) before approval.
  • Workflow integration: Reads pending todos from local directories such as .context/compound-engineering/todos/ and legacy todos/ and supports end-to-end triage before handoff to /todo-resolve.

Quick Start

Start the Todo Triage workflow to review each pending todo and decide whether to approve, skip, or modify.

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 code review todos effectively?▼

Triage pending todos by interactively reviewing severity, category, location, and proposed solutions, then deciding to approve, skip, or modify each item before moving it to ready.

What is the best way to prioritize engineering todos during a code review?▼

Prioritize engineering todos by evaluating each item's problem scenario, severity, and effort estimate, allowing you to approve, skip, or request modifications during the review workflow.

Can I use todo triage workflows with local project directories?▼

Yes, todo triage workflows read pending items directly from local directories such as .context/compound-engineering/todos/ and legacy todos/ to support end-to-end code review processing.

How do I update todo files after triaging them for code review?▼

Update todo files by triaging each pending item and applying a decision workflow that moves approved items to ready, deletes skipped items, or re-prompts for modifications.

What outcomes can I apply when reviewing pending todos?▼

You can apply three outcomes when reviewing pending todos: approve to move the item to ready, skip to delete it, or modify to re-prompt for adjustments before final approval.

Does todo triage integrate with downstream task resolution workflows?▼

Yes, todo triage supports end-to-end processing by updating approved items to ready, preparing them for handoff to downstream task resolution workflows like todo-resolve.

Related Skills

Explore More Software Engineering Skills→
All-The-VibesAll-The-Vibes
50

todo-resolve

Resolve ready todos in parallel and report pending items.

Official
Advanced
michaelvolzmichaelvolz

todo-resolve

Resolve ready todo items in compound engineering repositories.

Community
Advanced
dayvidphamdayvidpham
1

reviewer-review-code

Categorize code review findings into BLOCKER, IMPORTANT, and MINOR severity groups.

Community
Advanced
lossyroblossyrob
39

paw-review-github

Post finalized review comments from ReviewComments.md to GitHub as pending reviews.

Community
Advanced