"create ticket", "new issue", "bug", "story"?
WORKFLOW 1: Create Issue
← Skill registry
Business operationsPublic skills
Jira Project Tracking
Agile project management for AI agents — JQL search, sprint planning, issue lifecycle, velocity tracking, and cross-system coordination across GitHub and Slack.
What this skill teaches
A reusable playbook for a specific kind of work.
An MCP server tells an agent which actions are available. A skill adds the judgment around those actions: how to recognize the job, which sequence to follow, what to avoid, and how to decide that the result is complete.
Orchestrate Jira workflows — search issues with JQL, manage sprints, create and transition issues, track velocity, and coordinate agile ceremonies. Use when creating Jira tickets, searching issues, planning sprints, updating issue status, checking sprint progress, or managing project boards.
Architecture
How Jira Project Tracking guides an ADK-Rust agent.
The skill stays readable and portable because it contains instructions rather than service credentials or business data. ADK-Rust supplies it to the agent, the agent chooses from its reviewed tool boundary, and the connected MCP server performs the authenticated operation.
01
User request
The agent receives a goal expressed in ordinary language.
02
Jira Project Tracking skill
Matches intent, supplies the decision guide, and narrows the tool boundary.
03
ADK-Rust agent
Plans the workflow and streams each meaningful step through the runtime.
04
mcp-jira
Executes authenticated operations against the system that owns the capability.
05
Verified result
The skill's completion rules shape the evidence returned to the user.
Decision guide
How the agent turns a request into the right action.
These routes come directly from the skill instructions. They help the model recognize intent and select a focused tool or workflow instead of improvising across the entire capability surface.
"search", "find", "JQL", "issues where"?
WORKFLOW 2: Search Issues
"sprint", "plan", "velocity", "capacity"?
WORKFLOW 3: Sprint Management
"move", "transition", "done", "in progress"?
WORKFLOW 4: Transition Issue
"board", "kanban", "status"?
WORKFLOW 5: Board Overview
Unclear?
Ask: "Would you like to create a ticket, search issues, or manage a sprint?"
Proven workflows
Repeatable sequences for useful outcomes.
A workflow joins several tool calls into a task the user actually recognizes. The skill explains the sequence and the intended result while ADK-Rust streams the agent's progress through the shared runtime.
012 calls
Create Issue
Duplicate check + structured creation with AC
021 calls
Search Issues
JQL-powered queries for any filter
033-4 calls
Sprint Management
Velocity-aware planning + scope tracking
043 calls
Transition Issue
Valid state check + move + comment
052 calls
Board Overview
Current sprint status at a glance
Tool boundary
The skill may use 15 documented tools.
This allowlist is declared by the skill. It keeps the agent focused on the actions needed for this job while mcp-jira retains responsibility for authentication, validation, and the connected system.
list_projects
get_project
search_issues
get_issue
create_issue
update_issue
transition_issue
assign_issue
add_comment
list_comments
get_transitions
list_sprints
create_sprint
add_to_sprint
get_board
Working rules
What the agent should do.
- Follow the decision guide, use the declared tool boundary, and verify the result before responding.
Operating boundaries
What the agent should avoid.
- Review the complete SKILL.md before enabling this skill for production work.
Install and connect
Add the skill beside the capability it expects.
Install the repository where your ADK-Rust skill loader can discover it, connect mcp-jira, and confirm the declared tools are available before asking the agent to use the workflow.
Install the skill
git clone https://github.com/zavora-ai/skill-jira-project-tracking.git \
~/.skills/skills/jira-project-trackingADK-Rust loading shape
let skills = SkillLoader::from_dir("~/.skills/skills").await?;
let skill = skills.load("jira-project-tracking").await?;
let agent = LlmAgentBuilder::new("agent")
.instruction(skill.instructions())
.tools(skill.allowed_tools(toolset)?)
.build()?;The repository's compatibility statement: Requires mcp-jira server connected. Optional: mcp-github for PR linking, mcp-slack for sprint notifications.
Official documentation
Read the complete skill package.
The repository remains authoritative for its exact instructions, examples, helper scripts, assets, MCP requirements, license, and later updates.
Keep exploring
More in business operations.
Agriculture ManagementFarm operations for AI agents — field management, crop planning, weather intelligence, satellite monitoring (NDVI), commodity markets, IoT sensors, yield estimation, and pest/disease detection.34 allowed toolsBanking OperationsReal-time banking intelligence for AI agents — account monitoring, transaction analysis, anomaly detection, and payment initiation across Plaid (US/EU), Mono (Africa), and Open Banking (UK/EU).15 allowed toolsCRM Customer ManagementEnterprise CRM workflow orchestration for AI agents — customer 360 lookups, deal pipeline management, activity logging, and multi-MCP onboarding across Salesforce, HubSpot, Zoho CRM, and Pipedrive.27 allowed tools
Source record
Repository metadata for this skill entry.
- License
- Apache-2.0
- Allowed tools
- 15
- References
- 3
- Revision
- 5913deea9b1b
- Updated
- May 31, 2026