| name | triage-local |
| specializes | triage |
| description | Repo-specific triage guidance for this repository. Only the categories declared overridable below may be specialized here; the core triage contract (states, output shape, guardrails) is defined by the triage skill. |
Repo-specific triage guidance
This file is a companion to the core triage skill. It does not redefine
the readiness states, the structured output contract, or the safety
guardrails. It only specializes the categories listed below.
Tailor this file to your team as your factory runs: encode recurring
triage corrections here instead of editing the core triage skill, so
core skill updates stay easy to pull in from upstream.
Overridable categories
- Issue-type heuristics — recurring issue shapes in this codebase and how they typically route (e.g. "payment-related bugs always go to
Spec for a design pass").
- Follow-up question patterns — domain-specific details reporters routinely omit that block triage.
- Component ownership hints — mappings from product areas to owning teams or services that help identify the likely implementation area.
- Status conventions — deviations from the default status workflow, if your Jira project uses different names.
Current guidance
No repo-specific guidance has been captured yet. Add entries under the
categories above as your team observes recurring triage corrections.
