borghei/Claude-Skills / project-management/execution/issue-triage
issue-triage
VerifiedMove engineering issues and external PRs through a triage state machine and write agent-ready briefs. Use when clearing a triage queue, deciding if a report is real or wanted, or handing an issue to a coding agent.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.4 KB |
| assets/agent_brief_template.md | markdown | 2.1 KB |
| assets/label_scheme_template.md | markdown | 2.7 KB |
| assets/out_of_scope_entry_template.md | markdown | 1.6 KB |
| assets/sample_agent_brief_clean.md | markdown | 2.6 KB |
| assets/sample_agent_briefs.json | config | 2.8 KB |
| assets/sample_triage_history.json | config | 3.7 KB |
| assets/sample_triage_history_clean.json | config | 3.4 KB |
| assets/triage_notes_template.md | markdown | 2.1 KB |
| references/agent-briefs.md | markdown | 10.3 KB |
| references/evidence-and-out-of-scope.md | markdown | 9.2 KB |
| references/state-machine-and-labels.md | markdown | 10.4 KB |
| scripts/agent_brief_linter.py | script | 10.1 KB |
| scripts/triage_state_validator.py | script | 12.6 KB |
assets/agent_brief_template.md
View on GitHub# Agent Brief Template
Post this as a comment on the issue or pull request at the moment it moves to
`state:ready-for-agent` or `state:ready-for-human`. The brief is the contract;
the original report and thread are background. Lint it before posting:
```bash
python3 project-management/execution/issue-triage/scripts/agent_brief_linter.py --input brief.md
```
Rules of thumb while filling it in:
- Describe behaviour and contracts, never file paths or line numbers. The
issue may wait weeks; code moves, behaviour does not.
- Each acceptance criterion is one observable check that passes or fails on
its own. No "works", "correctly", "properly", "fast".
- Out of scope is mandatory. It is the fence that stops gold-plating.
- When the item is a pull request, use "Current behavior" for what the branch
already does, and scope the brief to the remaining work on that branch.
---
## Agent Brief
**ID:** <#issue or PR number>
**Target state:** ready-for-agent | ready-for-human
**Category:** bug | enhancement | chore | docs
**Summary:** <one line, under 120 characters, naming the observable change>
**Current behavior:**
<What happens today. For a bug: the broken behaviour plus the trigger that
reproduces it. For an enhancement: the status quo the change builds on. For a
PR: what the diff already does and which gaps remain.>
**Desired behavior:**
<What is true when the work is done, including edge cases and error paths.
State outcomes, not steps.>
**Key interfaces:**
- `<TypeOrFunction>` — <what changes in its contract, or "unchanged">
- <Config key, CLI flag, API field, event name the agent should look for>
**Acceptance criteria:**
- [ ] <Single observable check 1>
- [ ] <Single observable check 2 — usually an edge case or error path>
- [ ] <Regression guard: what must stay exactly as it is>
**Out of scope:**
- <Adjacent change the agent must not make>
- <Tempting refactor that belongs in another issue>
**Why not delegated:** <ready-for-human only — the judgment call, access,
manual test, or contract approval that keeps this with a person>
**Verification:** `<exact command or check that proves the criteria>`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |