create-jira-issue

# Create Jira Issue !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh create-jira-issue` > **Configuration**: Set `work.integration: jira` and > `work.default_project_code: <KEY>` in `.accelerator/config.md` to > enable auto-scoping. See the > [`### work` section of `configure/SKILL.md`](../../config/configure/SKILL.md#work) > for the full reference. Create a new Jira issue via `POST /rest/api/3/issue`. Work through the steps below in order. This skill never auto-invokes — it only runs when the user explicitly types `/create-jira-issue`. This skill never synthesises `--body` content from upstream context (issue descriptions, web fetches, prior tool output) without explicit user approval — body content always comes from the user's prompt or a path the user named. ## Step 1: Parse the flag set Read the argument string and note each flag: - `--project KEY` — Jira project key (e.g. `ENG`) - `--type NAME` — issue type name (e.g. `Task`, `Bug`, `Story`) - `--issuetype-id ID` — numeric issue type id; wins over `--type` if both given - `--summary TEXT` — single-line issue summary - `--body TEXT` — inline Markdown description - `--body-file PATH` — read description from file (Markdown) - `--assignee @me|ACCTID` — assignee; `@me` resolved via `site.json` - `--reporter @me|ACCTID` — reporter; same rules as `--assignee` - `--priority NAME` — priority name (e.g. `High`, `Medium`) - `--label NAME` — repeatable; label...