Skip to content

borghei/Claude-Skills / project-management/execution/issue-triage

issue-triage

Verified

Move 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.

assets/out_of_scope_entry_template.md

View on GitHub
# Out-of-Scope Register Entry Template

One entry per **concept**, not per issue. File name or key: a short
kebab-case concept name a newcomer would recognise (`per-user-themes`,
`plugin-runtime`, `graphql-api`). When a new request matches the concept,
append it to **Prior requests** instead of creating a second entry.

In JSON (what `triage_state_validator.py` reads under `out_of_scope_register`):

```json
{
  "concept": "per-user-themes",
  "decision": "rejected",
  "reason": "<durable reason: scope, architecture, or strategy, not 'busy right now'>",
  "revisit_if": "<the condition that would reopen the question>",
  "prior_requests": ["#212", "#239"]
}
```

As a markdown record:

```markdown
# <Concept name>

**Decision:** rejected — <one sentence stating what the project will not do>
**Decided:** <YYYY-MM-DD> by <role>

## Why
<Two or three short paragraphs. Name the constraint (scope, architecture,
cost, strategy) and the trade-off. A newcomer should understand it without
reading the original threads.>

## What we suggest instead
<Workaround, extension point, or downstream option, if one exists.>

## Revisit if
<The concrete change that would make this worth reopening, e.g. "runtime
rendering replaces build-time palette resolution".>

## Prior requests
- <#id> — "<title as the reporter phrased it>"
```

Checks before saving:

- The reason survives a change of team or quarter. "No capacity this
  quarter" is a deferral, not a rejection: keep the issue open and
  unprioritised instead.
- Bugs do not go here. A bug you will not fix is closed with an explanation.
- Already-implemented requests do not go here.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall