Move GitHub issues and external PRs through a triage state machine with agent-ready briefs.
npx skills add https://github.com/mikalv/pi-extensions --skill triage-mikalv
Please help me install this Agent Skill. Skill: triage Source: https://github.com/mikalv/pi-extensions/tree/main/packages/pi-atelier/.agents/skills/triage Command: npx skills add https://github.com/mikalv/pi-extensions --skill triage-mikalv
.out-of-scope/ knowledge base of prior rejections. - Agent brief generation: Writes durable, behavior-focused agent briefs with acceptance criteria and scope boundaries so AFK agents can implement changes without re-reading the whole thread. - Use Case: A maintainer runs the triage workflow on issue #42; the Skill reads the thread, reproduces the bug, checks .out-of-scope/ for prior rejections, grills the reporter for missing details, and posts a complete agent brief before labeling it ready-for-agent. ## Quick Start Ask the agent to triage issue #42 and move it to the appropriate state with an agent brief.High-intent search queries and answers about installing and using this skill.
Invoke the triage workflow with a natural-language request like "show me anything that needs my attention" or "look at #42". The Skill reads the full issue, verifies claims against the codebase, and recommends a category and state before applying labels and comments.
An agent brief is a structured comment posted when an issue reaches ready-for-agent state. It describes current and desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries so an autonomous agent can implement the change.
Yes, external PRs are treated as issues with attached code and move through the same states. The Skill checks out the diff, runs relevant tests to confirm it does what it claims, and writes briefs scoped to finishing the existing change.
Rejected enhancements are recorded as concept files in a `.out-of-scope/` directory with the decision, reasoning, and prior issue links. During triage, new requests are matched against these files by concept similarity and surfaced to the maintainer before re-litigating.
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.
phillip-hirschConfigure issue tracker, triage labels, and domain documentation for engineering skills.
NAMEWTAMoves GitHub issues and external PRs through a triage label state machine.
pedroscostaChallenge proposed plans against domain models and update CONTEXT.md and ADRs.
JohannesKoningsAutomate GitHub issue classification and state management with role-based workflows.