auth-jira git:20260515.4f3e739B

Immutable. This exact content is served forever at /api/v1/blob/3a22ad05db168a8c.

---
description: Interactive setup for Jira authentication. Prompts for domain, email, project key, and issue type, validates an Atlassian API token, and saves credentials. Run once per project before /specclaw:issue.
disable-model-invocation: true
---

# specclaw auth jira

**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.**

1. **Run:** `specclaw-auth-jira .specclaw`
   - Prompts for domain (e.g. `mycompany.atlassian.net`), email, project key, issue type.
   - Guides the user to `https://id.atlassian.com/manage-profile/security/api-tokens`.
   - Validates credentials and project key via Jira REST API.
   - Saves domain/email/project_key/issue_type to `config.yaml` under the `jira:` section; token to `.specclaw/.env` (gitignored).
2. Report success and suggest `/specclaw:issue <change>` as the next step.