issues · git:20261107.b47c639 · 2026-11-07 · sha256 1cb4ec0e6e7ec495

issues git:20261107.b47c639A

Immutable. This exact content never changes and is served at /api/v1/blob/1cb4ec0e6e7ec495.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2uypwx4khulyesqr/1cb4ec0e6e7ec49530508b9108f1d4cae33fc8ba74fc6b090068924b5fd7a0e4.json

Then /plugin install issues@markdownregistry-2uypwx4khulyesqr in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: issues
description: Use when opening an issue or changing its title or description.
---

# Issues

Whoever decides on an issue or picks it up, often an agent, reads it later without your context. Give it a plain-language title that names the problem or the desired outcome, and open the description with exactly these two paragraphs:

```md
**Problem.** The current behavior or missing ability, who or what it affects, and its concrete cost or risk.

**Outcome.** The observable result or decision that closes the issue.
```

The outcome says when the issue is done, not how. Name an implementation only when one is already decided, because whoever picks up the issue will treat a suggested approach as settled.

Put the support for the problem under `## Evidence`: observations, reproduction steps, measurements, code references, or sources, without restating the opening.

Add `## Decision` only when work can't start until someone makes a choice.