---
name: {PROJECT_KEY_LOWERCASE}:jira
version: "0.7.4"
description: JIRA issue management for the {PROJECT_KEY} project
disable-model-invocation: false
---

# JIRA Skill

Config-only skill — manage JIRA issues in the <PROJECT_KEY> project. Action: $ARGUMENTS

---

## Visual Framework

Follow the visual framework defined in the `output:visual-framework` primitive.

---

## Usage

```bash
/{PROJECT_KEY_LOWERCASE}:jira create "BE: Add auth endpoint" --type task   # Create a task
/{PROJECT_KEY_LOWERCASE}:jira get {PROJECT_KEY}-123                        # Fetch issue details
/{PROJECT_KEY_LOWERCASE}:jira search "sprint = active"                     # Search for issues
```

## Project Constants

- Project Key: <PROJECT_KEY>
- Board ID: <BOARD_ID>
- Assignee: <ASSIGNEE_NAME> (<ASSIGNEE_ID>)
- Label: <PROJECT_KEY> (always apply)

## Domain Prefixes for Titles

- BE: Backend
- FE: Frontend
- DB: Database
- DOC: Documentation
- BOT: AI/Bot
- INFRA: Infrastructure
- SEC: Security
- QA: Quality Assurance

## Rules

- Always apply <PROJECT_KEY> label
- Use domain prefix in title
- Never mention Claude, AI tools, or MCP in JIRA
- Use plain text tags: [STARTED], [COMPLETE], [BLOCKED]
- Include acceptance criteria as checklist
- Bugs MUST have a parent epic
- Always set assignee_id to the ASSIGNEE_ID from project-constants.md when creating issues
