issuerefinelisted

# Issue Refinement ## Arguments Parse `$ARGUMENTS`: - `--type bug|feature|refactor|spike`: skip type identification and read that guide directly. Default: infer the type from the description per [Issue Types](#issue-types). - `--compact`: force the trivial body per [Section Selection](#section-selection). Frontmatter is always emitted. 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 following the type's structure. 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 maps the frontmatter to tracker fields and saves the body. Defer all save mechanics to that skill. ## 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. ```markdown --- title: fix connection pool exhaustion under load # sentence case, one line, no long parentheticals type: bug # bug | feature | refactor | spike labels