jira-sdlc

Cache Jira project metadata to reduce repeated Atlassian MCP calls.

6|Updated Mar 4, 2026

Search Tags:#automation #mcp #cache #issues #jira #sdlc #workflows

Ready to run

npx skills add https://github.com/rnagrodzki/sdlc-marketplace --skill jira-sdlc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jira-sdlc
Source: https://github.com/rnagrodzki/sdlc-marketplace/tree/main/plugins/sdlc-utilities/skills/jira-sdlc
Command: npx skills add https://github.com/rnagrodzki/sdlc-marketplace --skill jira-sdlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira users need to manage many projects across tenants, and repeated Atlassian MCP calls slow down operations; this skill caches project metadata to speed up Jira actions and reduce API churn.

Core Features & Use Cases

Caches cloudId, siteUrl, project metadata, issue types, field schemas, workflows, link types, and user mappings for instant access
Supports multi-project repos via jira.projects and optional site disambiguation to map to multiple Jira tenants
Enables end-to-end Jira workflows: create, edit, search, transition, comment, link, assign, and log work using MCP
Applies templates and standardized description generation for new issues via templates and placeholders

Quick Start

Install and activate the jira-sdlc skill, then provide a --project key to initialize the cache and begin performing Jira operations with cached metadata.

Frequently Asked Questions about jira-sdlc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I reduce repeated Atlassian MCP calls when managing multiple Jira projects?▼

To reduce repeated Atlassian MCP calls, cache Jira project metadata like cloudId, issue types, and field schemas. This approach speeds up Jira actions across multiple projects and minimizes API churn by using validated cache data instead of live lookups.

Can I manage Jira workflows across multiple tenants using cached metadata?▼

You can manage Jira workflows across multiple tenants by caching site URLs and project metadata. The cache supports multi-project configurations and optional site disambiguation to map actions accurately to different Jira tenants.

How do I create and transition Jira issues using MCP without guessing field IDs?▼

To create and transition Jira issues without guessing field IDs, use validated cache data containing field schemas and workflows. The cache applies strict MCP parameter shapes derived from issue types and link types, ensuring accurate transitions and issue creation.

What Jira metadata needs to be cached for fast MCP issue search and assignment?▼

For fast MCP issue search and assignment, cache cloudId, siteUrl, project metadata, issue types, field schemas, workflows, link types, and user mappings. Validated cache data ensures correct user mappings and efficient issue searches.

Does this approach to Jira automation support applying standardized templates for new issues?▼

This Jira automation approach supports applying standardized templates for new issues. It uses cached field schemas and placeholders to generate standardized descriptions, ensuring new issues adhere to consistent formatting and workflow requirements.

What are the limitations of caching Jira metadata for MCP workflows?▼

A limitation of caching Jira metadata for MCP workflows is the reliance on strict parameter shapes, meaning operations require pre-validated cache data for issue types and workflows. The cache must be initialized with a project key before performing any actions.