issuelisted

# Issue File a new issue whose job is to convey *why* the work is needed and *how* the author intends to approach it — written for a reader who has never seen this part of the system. This is the singular, authoring counterpart to the `issues` skill: `issue` *drafts and writes* one issue (a new one, or an update to a known one), while `issues` *surveys the backlog* to find the next thing to work on. An issue describes work **to be done**, so unlike `commit` and `prepare-review` there is no diff to read from: the raw material is the author's intent, gathered up front. **Don't narrate your work.** Every step below is an operating instruction, not a script to read aloud — follow the execute-quietly discipline: `${CLAUDE_PLUGIN_ROOT}/guides/execute-quietly.md`. For this skill, the only things worth surfacing are a question you need answered, the drafted issue with its options, and the final URL. Issue = a GitHub issue or a GitLab issue. Pick the forge tool by the `origin` remote. ```mermaid %%{ init: { 'look': 'handDrawn' } }%% flowchart TD Start(["/issue"]) --> Mode{Issue ref given?} subgraph "Step 1: Resolve the issue" Mode -->|Yes| Update["Update: fetch current body as baseline"] Mode -->|No| Create["Create: new issue"] end subgraph "Step 2: Gather intent" Update --> Why["Ask the WHY + consumer + acceptance"] Create --> Why end subgraph "Step 3: Guard against duplicates" Why --> FromCreate{Creating a new is