From jira-tools
Create a well-structured Jira Objective with S.M.A.R.T criteria, key results, and milestones. Invoked internally by the /jira-create command. Objectives are the highest level of the work hierarchy, sitting above Initiatives, Epics, and Stories.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira-tools:create-jira-objectiveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Objectives represent the highest level of strategic work. They answer "what are we trying to achieve?" rather than "what are we building?". Every objective must be S.M.A.R.T and decompose into clear milestones that will each become a Jira Initiative.
Objectives represent the highest level of strategic work. They answer "what are we trying to achieve?" rather than "what are we building?". Every objective must be S.M.A.R.T and decompose into clear milestones that will each become a Jira Initiative.
Every objective MUST use this exact structure. Do not deviate.
## Description
[1-2 sentences. A high-level strategic outcome, written as a S.M.A.R.T goal: Specific, Measurable, Achievable, Relevant, and Time-bound.]
## Key Results
* [Measurable indicator that signals progress or completion — 1-3 items]
## Milestones / Phases
* **[Milestone name]** — [One sentence describing what this phase delivers. Each milestone maps to a Jira Initiative.]
Extract from the user's message or context passed from /jira-create:
Before drafting, check every S.M.A.R.T element:
Use AskUser for any gaps. Do not draft until all five S.M.A.R.T elements are present.
If the user has not provided milestones, ask:
If milestones are unclear, suggest 2-3 logical phases based on the objective and ask the user to confirm or adjust.
Write the description following the mandatory format. Before creating, review:
Use atlassian___createJiraIssue via the manage-jira skill:
issueTypeName: Use the issue type name provided by the active project skill, or discover it via atlassian___getJiraProjectIssueTypesMetadata if not specifiedprojectKey: From the selected project in /jira-createAfter 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.
/jira-create again for each one.manage-jira skill.npx claudepluginhub mbensch/mb-ai-tools --plugin jira-toolsConverts 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.
Use this skill when the user asks to "write OKRs", "structure our OKRs", "help with quarterly goals", "OKR review", "are our OKRs good", "how do I write key results", "our objectives and key results", "check our OKRs", or wants to create, review, or improve their OKR structure. Also use this skill when the user's roadmap items don't clearly connect to stated objectives.
Turns business goals into structured OKRs with measurable Key Results, initiatives, alignment checks, and anti-goals. Use for quarterly strategic planning.