From jira-tools
Create a well-structured Jira Initiative with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions and MCP-based ticket creation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira-tools:create-jira-initiativeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every initiative MUST use this exact structure. Do not deviate.
Every initiative MUST use this exact structure. Do not deviate.
## Background
[One paragraph. Strategic context: why this initiative exists, what problem or opportunity it addresses at the business or product level.]
## Objectives
* [Strategic objective this initiative is working toward]
* [Another objective]
## Key Results / Success Metrics
* [Measurable indicator that signals progress or completion]
* [Another metric]
## Out of Scope
[Only if the user explicitly calls out exclusions. Omit this section entirely otherwise.]
## Additional Information / Links
* [Strategy docs, OKRs, stakeholder contacts, related initiatives or epics]
h2., {{code}}, {code}, # for numbered lists). Use ## Heading, `code`, triple-backtick fenced code blocks, and 1. for numbered lists.Extract from the user's message or the context passed from /jira-create:
Use AskUser when genuinely ambiguous. Common questions:
Do NOT ask about format -- the format is fixed.
Write the description following the mandatory format. Before creating, review:
Use atlassian___createJiraIssue via the manage-jira skill for API mechanics:
issueTypeName: Always "Initiative"projectKey: Ask the user if not obvious from contextAfter creating the ticket, follow any post-creation steps defined by the active project skill (e.g. cars-project). These may include setting required custom fields such as team. If no project skill is active, skip this step.
manage-jira skill.npx claudepluginhub mbensch/mb-ai-tools --plugin jira-toolsInteractively writes structured tickets (story, bug, epic, initiative, subtask, issue) with type-specific fields and quality checks. Outputs clean Markdown ready for any tracker.
Converts Confluence spec pages into Jira backlogs with Epics and linked tickets. Use for generating backlogs from specs, breaking down requirements, or creating issues from Confluence.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.