triage

Classify observations into six triage classes and route them to downstream agents.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/iamsteveholmes/momentum --skill triage-iamsteveholmes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/triage
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill triage-iamsteveholmes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill batches a stream of observations, classifies each into one of six classes (ARTIFACT, DISTILL, DECISION, SHAPING, DEFER, REJECT), enriches ARTIFACT items with context, and coordinates batch approvals before delegating work or queuing items for later handling.

Core Features & Use Cases

  • Classifies items into ARTIFACT, DISTILL, DECISION, SHAPING, DEFER, or REJECT to support downstream routing.
  • Enriches ARTIFACTs with feature/epic/priority hints and suggests appropriate downstream actions.
  • Performs batch-approval before any execution and delegates ARTIFACT, DISTILL, and DECISION items to momentum:intake, momentum:distill, and momentum:decision respectively; SHAPING/DEFER/REJECT items are queued via intake-queue.
  • Writes SHAPING/DEFER/REJECT items to intake-queue.jsonl via the momentum-tools CLI when approved.

Quick Start

Invoke /momentum:triage with your list of observations to begin the triage workflow.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automatically classify and route backlog observations from retro findings or conversations?

To automatically classify and route backlog observations, batch-classify each item into ARTIFACT, DISTILL, DECISION, SHAPING, DEFER, or REJECT classes, then route them to the correct downstream agent or queue based on the classification result.

What is the best way to batch triage a stream of observations into distinct workflow categories?

Batch triage of observations works by evaluating a stream of items and assigning each to one of six routing classes, enriching ARTIFACT items with feature and priority hints, and coordinating batch approvals before delegating work downstream.

How do I queue deferred or rejected backlog items for later handling during intake routing?

To queue deferred or rejected items during intake routing, write SHAPING, DEFER, and REJECT classified observations to an intake-queue.jsonl file via the momentum-tools CLI after receiving batch approval.

Can I enrich backlog items with feature and epic context before delegating them to downstream agents?

Yes, you can enrich backlog items by applying feature, epic, and priority hints to ARTIFACT classified observations, passing this enriched context to downstream skills to suggest appropriate actions before delegation occurs.

How does batch approval work before delegating classified items to downstream workflows?

Batch approval requires reviewing all classified observations before execution, then delegating ARTIFACT, DISTILL, and DECISION items to their respective downstream skills while queuing SHAPING, DEFER, and REJECT items separately.

What are the limitations of using automated classification for backlog grooming and intake routing?

Automated classification for backlog grooming requires batch approval before any execution and relies on the momentum-tools CLI to write queued items, meaning unapproved items will not be delegated or persisted to the intake-queue.