jira-issue-refinelisted

# Jira Issue Refinement Turn one issue into a concise contract that an engineer or coding agent can implement and verify without guessing. Preserve confirmed intent, resolve discoverable facts, and expose decisions that still require a person. ## Establish the issue boundary 1. Read the complete draft or existing issue, including structured fields, comments, links, attachments, parent or child issues, and user-supplied context when available. 2. Identify the affected actor or system, current behavior, required outcome, business or operational reason, and requested issue type. 3. Separate confirmed requirements from observations, assumptions, implementation suggestions, and unrelated follow-up ideas. Do not silently promote an engineering suggestion into required behavior. 4. Preserve the author's confirmed intent and terminology. Change meaning only when evidence or an explicit user decision requires it. 5. Keep Jira access read-only unless the user explicitly authorizes creating or updating an issue. Do not implement the requested product or engineering change under this skill. ## Assess what the issue still needs Check each concern only to the depth material to delivery: - **Behavior:** State the observable result, inputs or preconditions, boundaries, failure behavior, and unchanged behavior. Do not reward detail that merely prescribes an implementation. - **Evidence:** For a bug, capture observed and expected behavior, reproduction, environment, diagnostics, and regr