monkilabs/jira-management
src/orchestrator/plugins/jira/SKILL.md
Create and update Jira issues, epics, and sprints; manage backlog and sprint transitions. Use when you say: 'create a ticket', 'open a story', 'link an epic', 'start a sprint', or 'search the backlog'.
$ install --global
skillsauthnpx skillsauth add monkilabs/opencastle jira-managementInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 9:18 AM27.3s3 files scanned
SKILL.md
- name:
- jira-management
- description:
- Create and update Jira issues, epics, and sprints; manage backlog and sprint transitions. Use when you say: 'create a ticket', 'open a story', 'link an epic', 'start a sprint', or 'search the backlog'.
<!-- ⚠️ This file is managed by OpenCastle. Edits will be overwritten on update. Customize in the .opencastle/ directory instead. -->
Task Management with Jira
For project-specific project keys, workflow state IDs, and board configuration, see tracker-config.md.
MCP Tool Examples
// Search issues
{ "jql": "project = PROJ AND status = 'In Progress' ORDER BY priority DESC" }
// Create issue
{ "project": "PROJ", "summary": "[UI] Build PriceRangeFilter", "type": "Task", "description": "Objective: ...\nFiles: ...\nAC: ..." }
// Transition issue
{ "issueKey": "PROJ-42", "status": "In Progress" }
Discovered Issues
Check Jira first; if untracked, create a [Bug] issue in Backlog with symptoms, repro steps, and affected files.
Issue Naming
Use [Area] Short description format in the Summary field:
[Schema] Add priceRange field to place type
[DB] Add price_range column and migration
[Query] Update query with priceRange filter
[UI] Build PriceRangeFilter component
[Page] Integrate price filter into /places
[Test] E2E test price range filtering
[Docs] Update data model documentation
Status Workflow
Backlog → To Do → In Progress → In Review → Done
Transition Rules
- Agent (via MCP):
To Do → In Progresson start;In Progress → Doneon verified completion. - Automation: PR events auto-update status when GitHub/Jira integration is configured.
- Link via Jira key in branch/PR title (e.g.,
PROJ-123).
Issue Descriptions
Every issue must include: Objective (one sentence), Files (partition) (paths this agent may modify), Acceptance Criteria (verifiable checklist), Dependencies (issue keys).
Group related issues under a Jira Epic; use components or labels for domain grouping.
Session Workflow
- Search the board (JQL) for existing in-progress work.
- Decompose the feature into issues; create all in Jira — verify each returns a valid issue key.
- Link dependencies between issues.
- Delegate: move issue to In Progress before starting; move to Done after verified.
- If creation/transition fails: retry once; check project key and workflow state IDs in tracker-config.md.
- On resume: search by status (In Progress, To Do), read descriptions, continue.
- On completion: verify all Epic issues are Done, run build/lint/test, close the Epic.
JQL Quick Reference
Common queries for agent workflows:
project = PROJ AND status = "In Progress" ORDER BY priority DESC
project = PROJ AND status = "To Do" ORDER BY priority DESC
project = PROJ AND type = Bug AND status != Done ORDER BY priority DESC
project = PROJ AND sprint in openSprints() ORDER BY priority DESC
project = PROJ AND priority = Highest AND status != Done
Related Skills
monkilabs/validation-gates
development
VerifiedTrustedCommunity
Defines 10 sequential validation gates: secret scanning, lint/test/build checks, blast radius analysis, dependency auditing, browser testing, cache management, regression checks, smoke tests. Use when running pre-deploy validation or CI checks, CI/CD pipelines, deployment pipeline validation, pre-merge checks, continuous integration, or pull request validation.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/testing-workflow
development
VerifiedTrustedCommunity
Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/team-lead-reference
development
VerifiedTrustedCommunity
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting delegation session, running multi-agent workflow, delegating work, choosing which model to use, or assigning tasks.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/session-checkpoints
testing
VerifiedTrustedCommunity
Saves, restores session state including task progress, file changes, delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.
44SKILL.mdUpdated Apr 21, 2026