triage

Triage change requests to select backlog, plan, ADR, or design artifact.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/fppfurtado/pragmatic-dev-toolkit --skill triage-fppfurtado
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/fppfurtado/pragmatic-dev-toolkit/tree/main/skills/triage
Command: npx skills add https://github.com/fppfurtado/pragmatic-dev-toolkit --skill triage-fppfurtado

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns intent and decides the appropriate artifact (backlog, plan, ADR, or domain/design update) before implementation.

Core Features & Use Cases

  • Produces a backlog entry, a plan, an ADR, or a domain/design update based on the change request.
  • Evaluates product direction, ubiquitous language, ADRs, and decisions to determine the minimal actionable artifact.
  • Guides interactions with local and canonical modes and supports branching logic for scope and artifact creation.

Quick Start

Describe the request briefly and I will determine whether to add a backlog line, create a plan, or raise an ADR.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I decide whether a change request needs a backlog entry, plan, or ADR?

Triage evaluates product direction, ubiquitous language, and existing ADRs to propose the minimal actionable artifact. It aligns intent and decides whether to create a backlog entry, plan, ADR, or domain/design update before implementation begins.

What is the best way to align intent before starting software implementation?

Aligning intent requires evaluating non-trivial change requests against product direction and ubiquitous language. Triage determines the correct artifact to produce, ensuring the next actionable step matches the scope and architectural needs of the request.

When do I need to create an ADR instead of a backlog item for a feature request?

You need an ADR when a change request impacts architectural decisions or existing domain design. Triage evaluates related ADRs and product direction to determine if an Architecture Decision Record is required instead of a simpler backlog line or plan.

Can I use triage to evaluate domain design updates for non-trivial changes?

Yes, triage evaluates non-trivial change requests against ubiquitous language and product direction to determine if a domain design update is necessary. It guides branching logic for scope and artifact creation within local and canonical modes.

How does triage handle change requests when product direction is unclear?

Triage may prompt for clarification when product direction or intent is unclear. It evaluates available decisions and ubiquitous language, communicating artifact recommendations to the planning workflow while supporting branching logic to resolve scope ambiguity.

Does triage support canonical and local modes for artifact creation?

Triage integrates with local and canonical modes to guide interactions during artifact creation. It determines whether to produce a backlog entry, plan, ADR, or domain/design update and communicates these recommendations directly to the planning workflow.