issuerefinelisted

# Issue Refinement Expand brief issue descriptions into structured issues for developers and AI agents. ## 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 tight body, a sentence or two that names the problem and points at the code, with no `## Context` frame. Frontmatter is always emitted. Default: size the body to the issue per [Section Selection](#section-selection). ## 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 1. Identify type and read the corresponding guide. When `--type` is set, use it and skip identification. 2. Gather context from code and related issues. Consolidate keyword variants into one or two broader searches per topic rather than a separate call per phrasing. Scan results by title and summary with a small result limit, and fetch full issue bodies only for the issues that will inform the refinement. 3. Draft refinement following the type-specific structure. Under `--compact`, produce the tight output described in [Section Selection](#section-selection). 4. Write `tmp/issue-<slug>.md`