Prefix: TIR- What it measures: how work enters the repository — issue
templates, PR templates, labels, and documented triage conventions.
Issue templates give agents a structured way to file bugs and feature requests. PR templates ensure every change carries the metadata reviewers (human or agent) need to evaluate it. Labels and triage conventions make the backlog navigable.
Criteria in this pillar
TIR-010 — Issue templates present
- Level: 2 · Scope: repository · Check: deterministic
.github/ISSUE_TEMPLATE/contains at leastbug_reportandfeature_requesttemplates.- Rationale: structured intake gives agents (triage, labeling, reproducing) enough consistent input to do meaningful work.
- Evidence expected: directory present with at least two templates.
TIR-020 — Pull request template
- Level: 2 · Scope: repository · Check: deterministic
.github/PULL_REQUEST_TEMPLATE.mdexists with at minimum: summary, related issues, and a pre-merge checklist.- Rationale: PR hygiene is one of the signals most strongly correlated with a healthy review culture.
- Evidence expected: file present; sections for summary, linking, checklist.
TIR-030 — Labels defined and documented
- Level: 3 · Scope: repository · Check: deterministic
- Labels are defined in
.github/labels.yml(or the repo's label set is documented) and synced to GitHub. - Rationale: consistent labels let agents filter, route, and prioritize — an ad-hoc label set makes automation unreliable.
- Evidence expected:
labels.ymlpresent; label-sync action configured.
TIR-040 — Triage convention documented
- Level: 4 · Scope: organization · Check: manual
- A documented triage process exists (owner, cadence, SLAs) and is followed — recent issues show triage labels applied within the SLA window.
- Rationale: untriaged backlogs are where agent-delegated work goes to die.
- Evidence expected: process document; issue label timestamps.
Related
- The 8 pillars — sibling pillars in v1.0.
- Criteria catalog — all criteria, one page.
- Maturity levels — how criteria combine into a level.