issue:refine

Issue Refinement

Arguments

Parse $ARGUMENTS:

• --type bug|feature|refactor|spike: use that type's guide. Default: infer the type per Issue Types.
• --compact: write the trivial body per Section Selection, still with frontmatter. Default: size the body to the issue.

Issue Types

Type	When to Use	Guide
Bug	Something is broken	bug.md
Feature	New capability	feature.md
Refactor	Internal improvement, no behavior change	refactor.md
Spike	Timeboxed investigation; output is a recommendation, not a shipped change	spike.md

Workflow

Read the type guide, gather context from code and related issues, and draft the refinement. Write it to tmp/issue-<slug>.md and output it for approval. After approval, hand the file to the platform skill (for Linear, linear:linear), which owns all save mechanics, including mapping frontmatter to tracker fields. On GitHub, a screenshot the body references by local path goes on gh issue create --attach, per github:attach.

Output Structure

YAML frontmatter for the metadata a tracker stores as fields, then the body below the closing ---. The body leads with the summary prose directly, under no heading.

---
title: fix connection pool exhaustion under load   # sentence case, one line, no long parentheticals
type: bug                                           # bug | feature | refactor | spike
labels: [performance, database]                     # optional; neutral tags
priority: high                                      # optional; urgent | high | medium | low
relations:                                          # optional; tracker links per relation
  blocks: []
  blocked-by: []
  related:
    - https://linear.app/acme/issue/ENG-1970
  duplicate-of: []
---

The nightly export marks its run successful even when per-object retrievals
time out, so downstream jobs read a partial snapshot as if it were complete.

[Type-specific sections from guide (select, don't fill)]

## 🤖 Agent Context