triage

Classify development tasks into DO_IT_NOW, LITE_SPEC, or METAPLAN routes.

1|Updated Apr 13, 2026

Search Tags:#routing #agile #triage #development-workflow #task-classification #planning-depth

Ready to run

npx skills add https://github.com/t-uda/skills --skill triage-t-uda

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/t-uda/skills/tree/main/skills/triage
Command: npx skills add https://github.com/t-uda/skills --skill triage-t-uda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify an incoming development task into one of three routes: DO_IT_NOW, LITE_SPEC, or METAPLAN to keep planning overhead proportional to task difficulty.

Core Features & Use Cases

Route classification and guidance to select the appropriate planning depth for a task.
Evaluation criteria including Ambiguity, Blast radius, Reversibility, Interruption risk, and Review value.
Clear examples and guidance for common scenarios (small edits, medium features, architecture changes, etc.).

Quick Start

Describe the task and context, and I will assign the appropriate routing path (DO_IT_NOW, LITE_SPEC, or METAPLAN).

Frequently Asked Questions about triage

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

FAQPage Schema

How do I decide the right planning depth for a development task?▼

Task routing classifies development work into three planning paths: DO_IT_NOW for small edits, LITE_SPEC for medium features, and METAPLAN for architectural changes. This prevents under-planning complex work and over-planning simple fixes.

How do I route incoming development tasks based on ambiguity and scope?▼

When should I use a lite spec versus a metaplan for feature work?▼

What is the best way to classify agile development tasks by impact and reversibility?▼

Can I use task classification routing for small code edits and architectural changes alike?▼

Why does task planning overhead become disproportionate to task difficulty?▼