triage

Move issues through a state machine of roles and write agent-ready briefs.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/petemcw/farseer --skill triage-petemcw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/petemcw/farseer/tree/main/skills/triage
Command: npx skills add https://github.com/petemcw/farseer --skill triage-petemcw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Issue trackers accumulate unreviewed, ambiguous, or duplicate reports that stall development. This Skill moves issues through a defined state machine of roles, verifies claims against the codebase, and converts approved work into durable agent-ready briefs. ## Core Features & Use Cases - State Machine Triage: Categorize issues as bug or enhancement and move them through needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix states. - Codebase Verification: Reproduce reported bugs, check for redundant existing implementations, and match requests against a persistent out-of-scope knowledge base of prior rejections. - Agent Brief Generation: Write durable, behavior-focused specifications with acceptance criteria that autonomous agents can execute weeks later. - Use Case: A maintainer asks "Show me anything that needs my attention" and receives three buckets of unlabeled, in-progress, and re-activated issues, then triages issue #42 into a ready-for-agent brief after verifying the bug in the codebase. ## Quick Start Ask the assistant to triage issue number 42 on the project issue tracker and move it to the appropriate state.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage GitHub issues with an AI assistant?▼

Invoke the triage command and describe what you want in natural language, such as showing issues needing attention or examining a specific issue number. The assistant reads the full issue, verifies claims against the codebase, and recommends a category and state.

What is an agent brief for autonomous issue resolution?▼

An agent brief is a structured comment posted when an issue moves to ready-for-agent. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries, avoiding file paths and line numbers that go stale.

How does the out-of-scope knowledge base prevent duplicate feature requests?▼

Rejected enhancements are recorded as concept files in .farseer/out-of-scope/ with the decision, reasoning, and prior issue links. During triage, new issues are matched against these files by concept similarity so prior rejections surface instead of being re-litigated.

Can I override the triage state of an issue directly?▼

Yes, a maintainer can say something like move issue 42 to ready-for-agent and the role is applied directly after confirmation. The interview step is skipped, though you will be asked whether to write an agent brief.

When should an issue be marked ready-for-human instead of ready-for-agent?▼

Use ready-for-human when the work requires judgment calls, external access, design decisions, or manual testing that an autonomous agent cannot perform. The brief follows the same structure but notes why delegation is not possible.