Add jira:refine command for enhancing partially defined issues

Introduce new /jira:refine subcommand that intelligently enhances
incomplete or under-specified JIRA stories, tasks, and bugs by adding
missing critical information while preserving existing good content.

Key capabilities:
- Analyzes issue quality (description, acceptance criteria, fields)
- Adds user story format for stories (As a... I want... So that...)
- Generates testable acceptance criteria based on context
- Sets missing fields (priority, component, story points, epic links)
- Provides interactive refinement workflow with preview
- Preserves existing content - enhancement, not replacement

This complements the jira:create command by helping teams improve
backlog quality during grooming sessions and convert stub tickets
from automation into actionable work items.

Files added:
- plugins/jira/commands/refine.md
- plugins/jira/skills/refine-issue/SKILL.md

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Author: rvanderp3

PLUGINS.md

@@ -164,6 +164,7 @@ A plugin to automate tasks with Jira
 - **`/jira:generate-feature-doc` `<feature-key>`** - Generate comprehensive feature documentation from Jira feature and all related issues and PRs
 - **`/jira:generate-test-plan` `[JIRA issue key] [GitHub PR URLs]`** - Generate test steps for a JIRA issue
 - **`/jira:grooming` `[project-filter] [time-period] [--component component-name] [--label label-name] [--type issue-type] [--status status] [--story-points]`** - Analyze new bugs and cards added over a time period and generate grooming meeting agenda
+- **`/jira:refine` `<issue-key> [<issue-key>...]`** - Refine partially defined JIRA issues with complete descriptions and acceptance criteria
 - **`/jira:solve`** - Analyze a JIRA issue and create a pull request to solve it.
 - **`/jira:status-rollup` `issue-id [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD]`** - Generate a status rollup comment for any JIRA issue based on all child issues and a given date range
 - **`/jira:validate-blockers` `[target-version] [component-filter] [--bug issue-key]`** - Validate proposed release blockers using Red Hat OpenShift release blocker criteria

docs/data.json

@@ -132,6 +132,12 @@
           "name": "grooming",
           "synopsis": "/jira:grooming [project-filter] [time-period] [--component component-name] [--label label-name] [--type issue-type] [--status status] [--story-points]"
         },
+        {
+          "argument_hint": "<issue-key> [<issue-key>...]",
+          "description": "Refine partially defined JIRA issues with complete descriptions and acceptance criteria",
+          "name": "refine",
+          "synopsis": "bash"
+        },
         {
           "argument_hint": "",
           "description": "Analyze a JIRA issue and create a pull request to solve it.",
@@ -225,6 +231,11 @@
           "description": "Jira conventions and bug templates for the OCPBUGS project",
           "id": "ocpbugs",
           "name": "OCPBUGS Jira Conventions"
+        },
+        {
+          "description": "Implementation guide for refining partially defined stories, tasks, and bugs with complete descriptions and acceptance criteria",
+          "id": "refine-issue",
+          "name": "Refine Jira Issue"
         }
       ],
       "version": "0.0.1"