triage

Classify incoming requests into canonical labels and output an ordered routing plan.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/remiboivin021/synexis --skill triage-remiboivin021
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/remiboivin021/synexis/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/remiboivin021/synexis --skill triage-remiboivin021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage helps route incoming requests safely and deterministically by classifying types, detecting governance triggers, and guiding the next steps in the skill flow.

Core Features & Use Cases

  • Classify requests into canonical labels (FEATURE, BUG, REFACTOR, PERF, SECURITY, DOC, RELEASE, ADR).
  • Detect governance, architecture, security, and documentation triggers to enforce proper gating.
  • Output an explicit ordered routing plan that minimizes risk and ensures auditable decisions.

Quick Start

Ask for the incoming request text and any governance context, then produce a single, auditable routing plan.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I route incoming software requests safely and deterministically?

Deterministic request triage works by evaluating governance, architecture, and security triggers to classify incoming requests into a single canonical label, then outputting an ordered routing plan with required gates for safe execution.

What is the best way to enforce governance and security gates in a development workflow?

Enforcing governance and security gates requires detecting architecture and documentation triggers during request classification, then producing an explicit ordered routing plan that minimizes risk and maintains auditable traceability for safe execution.

How do I classify software requests into categories like bug, feature, or security?

Classify software requests by evaluating governance, architecture, and documentation triggers to assign a single canonical label such as FEATURE, BUG, REFACTOR, PERF, SECURITY, DOC, RELEASE, or ADR for deterministic routing.

Can I generate an auditable routing plan for software architecture decisions?

Yes, you can generate an auditable routing plan by classifying the request type, detecting architecture and governance triggers, and outputting an exact ordered flow with required gates and assumptions that ensures traceability.

Why does request routing fail to maintain traceability without deterministic classification?

Request routing loses traceability when it skips canonical label classification and governance trigger detection, leading to unsafe routing paths that lack an explicit ordered plan with required gates and auditable assumptions.

When should I avoid automated request triage in my software workflow?

Avoid automated request triage when incoming requests lack sufficient governance context or documentation triggers, as the classification requires evaluating these inputs to determine the minimal valid flow and produce a safe, auditable routing plan.