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.
npx claudepluginhub mbensch/mb-ai-tools --plugin jira-toolsThis skill uses the workspace's default tool permissions.
Every initiative MUST use this exact structure. Do not deviate.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Provides patterns for autonomous Claude Code loops: sequential pipelines, agentic REPLs, PR cycles, de-sloppify cleanups, and RFC-driven multi-agent DAGs. For continuous dev workflows without intervention.
Applies NestJS patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production TypeScript backends with project structure and bootstrap examples.
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.