From specclaw
Walks through Jira authentication setup: prompts for domain, email, project key, issue type, validates API token, and saves credentials. One-time setup before using /specclaw:issue.
How this skill is triggered — by the user, by Claude, or both
Slash command
/specclaw:auth-jiraThe 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).
Interactive Jira authentication setup. Guides the user to create an Atlassian API token, validates it, and saves credentials.
The user must run this command themselves in a real terminal — specclaw-auth-jira refuses to run without /dev/tty because it prompts for an API token. If you (the agent) try to invoke it, the script exits with instructions for the user. Just tell the user to open their shell and run specclaw-auth-jira .specclaw directly.
specclaw-auth-jira .specclaw
mycompany.atlassian.net), email, project key, issue type.https://id.atlassian.com/manage-profile/security/api-tokens.config.yaml under the jira: section; token to .specclaw/.env (gitignored)./specclaw:issue <change> as the next step.npx claudepluginhub chan4lk/specclaw --plugin specclawManage Jira issues, boards, sprints, and projects via the jira-cli. Search, create, update, and transition issues directly from the command line.
Sets up Jira Cloud integration: verifies credentials, discovers custom fields and projects, caches results as version-controlled JSON. Idempotent and safe to re-run.
Creates a Jira issue from a specclaw proposal, building summary and description from proposal.md and spec.md. Idempotent and requires Jira credentials.