todo-triage

Triage pending todo findings by severity and readiness status.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill todo-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-triage
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/todo-triage
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill todo-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps pending todos from stalling approvals by guiding focused review, enforcing severity awareness, and ensuring only ready work items move forward.

Core Features & Use Cases

  • Interactive Review: Presents each pending todo with severity, category, description, location, scenario, solution, and effort so reviewers stay aligned with context.
  • Decision Enforcement: Renames files and frontmatter for approved items, deletes skipped todos, and prompts for custom modifications when needed.
  • Use Case: While preparing a release, run this triage to confirm only the most critical findings are approved as ready work items and capture skip rationale for the rest.

Quick Start

Review the pending todos in .context/compound-engineering/todos/ and todos/ to decide for each whether to approve, skip, or modify before summarizing the final outcomes.

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 todo items to prioritize code review approvals?

To triage pending todos for prioritized approvals, this Skill reviews entries in .context/compound-engineering/todos/ and todos/ directories by presenting severity and readiness status, then updates file names and frontmatter for approvals while deleting skipped items.

What is the best way to manage issue prioritization and severity tracking for pending todos?

Issue prioritization and severity tracking for pending todos is managed by interactively presenting each finding's severity, category, description, and effort, allowing you to approve, skip, or modify items before summarizing final outcomes.

How do I update todo frontmatter and file names to ready status for approvals?

You update todo frontmatter and file names to ready status by approving items through the interactive review workflow, which automatically modifies file names and frontmatter to reflect their readiness for approvals.

Can I skip pending todo findings and capture the rationale during a release review?

Yes, you can skip pending todo findings during a release review and capture the rationale, as the workflow deletes skipped items and summarizes approvals and skips with status details.

What context is presented for each pending todo during workflow guidance for code review?

During workflow guidance for code review, each pending todo presents severity, category, description, location, scenario, solution, and effort so reviewers stay aligned with the necessary context to make decisions.

What happens to skipped todo files after triage decisions are finalized?

After triage decisions are finalized, skipped todo files are permanently deleted from the todos directory, while approved items have their file names and frontmatter updated to ready for approvals with a summary of outcomes.