From jira-tools
Create a well-structured Jira Epic with consistent formatting optimized for both human readers and AI agents. Invoked internally by the /jira-create command. Handles clarifying questions, optional codebase investigation, and MCP-based ticket creation.
npx claudepluginhub mbensch/mb-ai-tools --plugin jira-toolsThis skill uses the workspace's default tool permissions.
Every epic 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 epic MUST use this exact structure. Do not deviate.
## Background
[1-3 paragraphs. Business context, strategic driver, or user need that motivates this body of work.]
## Goals
* [Concrete goal or outcome this epic aims to achieve]
* [Another goal]
## Acceptance Criteria
* [High-level, testable condition that signals the epic is complete]
* [Another condition]
## Additional Information / Links
* [Designs, documentation, dependencies, related tickets or initiatives, out-of-scope items]
h2., {{code}}, {code}, # for numbered lists). Use ## Heading, `code`, triple-backtick fenced code blocks, and 1. for numbered lists.feat: prefix.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. Do NOT ask questions you can answer by investigating the codebase.
If codebase analysis was requested during /jira-create, always investigate:
Write the description following the mandatory format. Before creating, review:
Use atlassian___createJiraIssue via the manage-jira skill for API mechanics:
issueTypeName: Always "Epic"parent: Set when the user provides a parent initiativeprojectKey: Derive from the parent ticket's project, or ask the userAfter 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.manage-jira skill.