From sprint-jira
Authenticates against Jira Cloud REST API v3 using JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN environment variables. Validates board and project access. Fails immediately with a clear error listing all three required env vars if any are missing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sprint-jira:jira-connectorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Authenticates against Jira Cloud and validates that the configured board and project are accessible before any sprint data is fetched.
Authenticates against Jira Cloud and validates that the configured board and project are accessible before any sprint data is fetched.
| Variable | Description |
|---|---|
JIRA_BASE_URL | Jira Cloud base URL, e.g. https://your-org.atlassian.net |
JIRA_EMAIL | Account email used for Basic Auth |
JIRA_API_TOKEN | API token (not account password) |
If any variable is missing, halt immediately:
ERROR: Jira authentication requires three environment variables:
JIRA_BASE_URL — e.g. https://your-org.atlassian.net
JIRA_EMAIL — your Jira account email
JIRA_API_TOKEN — create at: id.atlassian.com/manage-profile/security/api-tokens
Run /sprint-init to verify your setup.
Jira Cloud uses HTTP Basic Auth with email + API token:
Authorization: Basic base64(JIRA_EMAIL:JIRA_API_TOKEN)
Content-Type: application/json
JIRA_BASE_URL is a valid HTTPS URL ending with .atlassian.netGET {baseUrl}/rest/api/3/myself to verify credentialsGET {baseUrl}/rest/agile/1.0/board/{boardId} to confirm board exists and is accessibleGET {baseUrl}/rest/api/3/project/{projectKey} to confirm project existsFor each validation failure, emit a specific error message describing which check failed and what to verify.
{
"authenticated": true,
"baseUrl": "https://your-org.atlassian.net",
"boardId": 42,
"projectKey": "PROJ",
"boardName": "PROJ Sprint Board",
"projectName": "My Project"
}
npx claudepluginhub gagandeepp/software-agent-teams --plugin sprint-jiraGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.