From jira-tools
Create a well-structured Jira Story 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 story 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 story MUST use this exact structure. Do not deviate.
## Background
[One paragraph. Context, business need, or user motivation. Short as possible.]
## Acceptance Criteria
* [Concrete, testable, outcome-oriented requirement]
* [Another requirement]
## Out of Scope
[Only if the user explicitly calls out exclusions. Omit this section entirely otherwise.]
## Additional Information / Links
* [Designs, documentation, dependencies, related tickets]
h2., {{code}}, {code}, # for numbered lists). Use ## Heading, `code`, triple-backtick fenced code blocks, and 1. for numbered lists.feat: / fix: prefix.Extract from the user's message:
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.
When the story involves technical changes in the current repo:
Skip this step for non-technical stories or stories targeting a different repo.
Write the description following the mandatory format. Before creating, review:
Use atlassian___createJiraIssue via the manage-jira skill for API mechanics:
issueTypeName: Always "Story"parent: Set when provided by the userassignee_account_id: Set when the user requests assignment (look up from an existing ticket if needed)projectKey: 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.