From specclaw
Creates a Jira issue from a specclaw proposal, building summary and description from proposal.md and spec.md. Idempotent and requires Jira credentials.
How this skill is triggered — by the user, by Claude, or both
Slash command
/specclaw:issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
Create a Jira issue from a specclaw proposal. Requires proposal.md (run /specclaw:propose first).
status.md already records a Jira issue for this change, warn and skip.specclaw-jira-issue .specclaw <change>
JIRA_TOKEN, JIRA_URL, JIRA_EMAIL, JIRA_PROJECT (set via /specclaw:auth-jira).proposal.md.proposal.md + spec.md (if present).**Jira Issue:** [KEY](url) to status.md.npx claudepluginhub chan4lk/specclaw --plugin specclawCreates Jira issues via CLI flags or work-item files. Converts Markdown body to ADF, previews payload, requires confirmation, then POSTs to Jira.
Creates Jira issues (story, bug, epic, etc.) with team-specific conventions (CNTRLPLANE, OCPBUGS, GCP, HyperShift, ARO, ROSA) and type-specific templates. Automatically applies labels, security fields, and smart defaults.
Creates, reads, updates, and deletes single Jira issues (bugs, tasks, stories). Use for quick issue management without leaving the terminal.