oprogramadorreal/optimus-claude / skills/jira
jira
VerifiedFetches a JIRA issue via a configured MCP server and distills it into a structured task file at docs/jira/<KEY>.md that downstream skills auto-detect. Analyzes the codebase to surface missing criteria, scope, and risks; optionally writes an analysis comment or implementation tickets back to JIRA after explicit confirmation. Re-runs reconcile the local file instead of regenerating. Guides MCP setup if none is configured.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 6.9 KB |
| SKILL.md | skill md | 6.3 KB |
| agents/openai.yaml | config | 198 B |
| references/jira-codebase-analysis.md | markdown | 6.9 KB |
| references/jira-context-extraction.md | markdown | 8.0 KB |
| references/jira-implementation-tickets.md | markdown | 6.3 KB |
| references/jira-refresh.md | markdown | 7.6 KB |
| references/jira-setup.md | markdown | 3.0 KB |
| references/plan-mode-prompt.md | markdown | 1.0 KB |
references/jira-setup.md
View on GitHub# JIRA MCP Setup
Read only when the Detection Procedure in `jira-context-extraction.md` found no JIRA MCP server. Guides first-time setup, then re-runs detection.
## Choose a server
Ask the user (AskUserQuestion) which server to set up:
- **Atlassian Rovo (recommended)** — official, cloud-hosted, OAuth 2.1; JIRA Cloud only (`*.atlassian.net`)
- **mcp-atlassian (community)** — open-source (sooperset); JIRA Cloud AND Server/Data Center; runs locally via uvx or Docker
- **Skip setup** — stop the skill and tell the user to re-run `/optimus:jira` after configuring a server (setup commands are also in this skill's README)
The user runs the chosen command in their own terminal; never ask for, accept, or run a command containing their API token or PAT.
## Atlassian Rovo
```
claude mcp add --transport http --scope user atlassian https://mcp.atlassian.com/v1/mcp
```
- Use `--transport http` (Streamable HTTP) with the `/v1/mcp` endpoint — the older SSE transport (`/v1/sse`) is deprecated by Atlassian and has reconnect issues on Windows. If tools never appear after an apparently successful setup, an SSE registration is the likely cause: remove and re-add with `--transport http`.
- The org admin must enable the server first: `admin.atlassian.com → Apps → AI settings → Rovo MCP server`.
- Auth is OAuth 2.1 — no JIRA tools appear until the user runs `/mcp` and authenticates `atlassian` in the browser. All actions respect the user's existing JIRA permissions.
- Team-shared config: use `--scope project` to write `.mcp.json` instead. Safe to commit — OAuth tokens are never stored in `.mcp.json`; each teammate completes their own consent flow.
## mcp-atlassian
For JIRA Cloud (API token from https://id.atlassian.com/manage-profile/security/api-tokens):
```
claude mcp add-json mcp-atlassian '{
"command": "uvx",
"args": [
"mcp-atlassian",
"--jira-url=https://YOUR-COMPANY.atlassian.net",
"--jira-username=your.email@company.com",
"--jira-token=YOUR_API_TOKEN"
]
}'
```
For JIRA Server/Data Center: same command with `--jira-url=https://your-jira-server.com` (base URL, include the port if non-standard) and `--jira-personal-token=YOUR_PAT` (Personal Access Token from the JIRA profile page) replacing the username/token args.
- **Token hygiene:** the token lands in shell history — clear the entry afterwards, or hand-write `.mcp.json` with `${JIRA_USERNAME}`/`${JIRA_API_TOKEN}` environment-variable placeholders so no real token is ever committed.
- Docker alternative: `"command": "docker"`, `"args": ["run", "-i", "--rm", "-e", "JIRA_URL=...", "-e", "JIRA_USERNAME=...", "-e", "JIRA_API_TOKEN=...", "ghcr.io/sooperset/mcp-atlassian:latest"]` (use `JIRA_PERSONAL_TOKEN` for Server/DC).
## Verify
When the user reports setup complete, run the Detection Procedure again. If tools are still missing, suggest restarting Claude Code (MCP servers may need a fresh session) and checking `claude mcp list`; troubleshoot from the actual error output. If the user gives up or skips, stop the skill.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |