triage

Route incoming requests into workflow entry phases and record state for downstream execution.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill triage-friedbotstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/triage
Command: npx skills add https://github.com/friedbotstudio/baseline --skill triage-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity from incoming requests by classifying the work into the correct workflow entry phase and preparing the state that downstream skills and guards need.

Core Features & Use Cases

  • Workflow Routing: Distinguishes between new features, bug fixes, quickfixes, chores, freeform batches, epic work, and epic-child follow-ups.
  • State Preparation: Writes the workflow state file so the rest of the Claude Code workflow can read the chosen track and exceptions.
  • Git-Aware Control Flow: Detects non-git projects and adjusts consent-gated phases accordingly, preventing invalid commit-path execution.
  • Tasklist Seeding: Loads canonical tracks from workflows.jsonl and materializes the correct task sequence for the chosen request type.

Quick Start

Ask the triage skill to classify my request, write the workflow state, and tell me which next phase to run.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I route incoming requests into the correct workflow in Claude Code?

Tasklist seeding loads canonical tracks from a .claude/workflows.jsonl file and materializes the correct task sequence for the chosen request type. This ensures the workflow state file contains the exact tasks required for downstream execution.

How does git-aware consent gating handle non-git projects?

Git-aware consent gating detects non-git projects and adjusts consent-gated phases accordingly. This prevents invalid commit-path execution, ensuring that workflow tracks requiring git operations do not run incorrectly in non-git environments.

What workflow tracks are available for classifying software engineering tasks?

Available workflow tracks for classifying tasks include new features, bug fixes, quickfixes, chores, freeform batches, epic slicing, and epic-child follow-ups. Track selection is required to properly route the request into the correct entry phase.

Do I need a .claude/workflows.jsonl file to use workflow routing?

Yes, a .claude/workflows.jsonl file is required for tasklist seeding. The workflow routing process loads canonical tracks from this file to materialize the correct task sequence for the chosen request type within your repository.

Why does my workflow state file need to be written before downstream execution?

The workflow state file must be written during triage so downstream skills and guards can read the chosen track and exceptions. Without this state preparation, subsequent phases lack the context needed to execute the correct workflow path.