issues · v2.1.1 · 2026-10-15 · sha256 c37f385a80ccf005

issues v2.1.1A

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

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_b62rh3fa4swxrmx4/c37f385a80ccf0058a33e07f85db96210c41ee79770447cb29f69d163d32599a.json

Then /plugin install issues@markdownregistry-b62rh3fa4swxrmx4 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
version: 2.1.1
description: Turn an agreed outcome into tracker issues with acceptance, dependencies, references, and verification. Keep planning proportional to the work.
argument-hint: "[task-or-spec-reference]"
recommended: true
---

# Issues

Publish agreed work in the project's tracker. Do not build or restart a design interview.

Read AGENTS.md, docs/agents/issue-tracker.md, and docs/agents/triage-labels.md when present. Use their commands and conventions. Otherwise infer the tracker from the remote and available tools; ask only when the destination or intended scope is genuinely ambiguous. Add a short tracker pointer to AGENTS.md if needed. Do not scaffold empty context files or pipeline state.

Fetch a referenced spec or issue with its comments. Inspect relevant source and test configuration. Respect existing decision docs. Identify a specific missing product decision rather than inventing acceptance criteria.

One issue is enough for one coherent task. Split when dependencies, independent ownership, or separately verifiable delivery warrant it. Use a parent spec when it helps explain a multi-issue effort. File and code references are welcome when they save rediscovery.

Each issue contains:

- Outcome and expected behavior.
- Checkable acceptance and important boundaries.
- Relevant issue, design, source, and test references.
- Dependencies, or an explicit statement that it can start.
- A Verification-command derived from existing checks, plus runtime or manual acceptance when needed. A build pass must not masquerade as behavior verification. When the repo has a `verify-<app>` skill, name the feature that proves this issue (`.cursor/skills/verify-<app>/features/<feature>.md`) in Verification.

Present a substantial breakdown once. Honor existing publishing authority and approval; do not ask again for already authorized work. Publish blockers first and use the repo's ready label, such as ready-for-agent, with all required label axes. Avoid a duplicate local backlog and an extra closeout comment repeating the published issues.

Return issue URLs and a concise starting instruction, such as /ship #123. Start the next stage only when requested.