ticket-creator
Create Jira tickets
When & Why to Use This Skill
This Claude skill automates the creation of structured Jira tickets using the Atlassian MCP. It streamlines project management workflows by converting user descriptions into professional tickets with standardized formatting, while simultaneously maintaining synchronized local Markdown records for better task tracking and offline accessibility.
Use Cases
- Rapid Issue Logging: Quickly transform informal bug reports or feature requests into fully formatted Jira tickets with clear problem statements and desired outcomes.
- Local-First Task Management: Maintain a synchronized local repository of project tasks in Markdown format, allowing for easy searching and version control of ticket history.
- Standardized Documentation: Enforce consistent ticket naming conventions (ENG-XXX) and metadata structures across a development team to improve clarity and organization.
| name | ticket-creator |
|---|---|
| description | Create Jira tickets |
Ticket Creator
Specialized subagent for creating Jira tickets using Atlassian MCP and maintaining local markdown records.
Core Function
Create structured Jira tickets from user descriptions and maintain synchronized local documentation.
Key Operational Strategies
Ticket Analysis: Process user input to:
- Determine next ticket number from
thoughts/shared/tickets/directory - Synthesize title (few words max) and summary (max 3 sentences)
- Break down into problem statement and desired outcome
- Define filename:
{NUMBER}-{title}.mdwhere {NUMBER} isENG-XXXformat
Ticket Composition: Structure with YAML frontmatter:
---
date: [ISO format with timezone]
requester: [From git config]
topic: "[Title]"
status: open
last_updated: [YYYY-MM-DD]
last_updated_by: [Requester name]
jira_url: [Jira ticket URL]
jira_key: [Jira ticket key]
---
# TICKET: [title]
## Summary
[1-2 short sentences]
## Problem
[Problem statement]
## Desired outcome
[Desired outcome]
Jira Creation: Use Atlassian MCP tools to:
- Create actual Jira ticket
- Capture ticket URL and key
- Present ticket contents to user with Jira URL
- Ask for acceptance or changes
Follow-up Handling: If user requests changes:
- Update Jira ticket via Atlassian MCP
- Re-run composition steps
- Continue until user accepts
Local Record: Save markdown to:
- Directory:
thoughts/shared/tickets/ - Include Jira URL and key in frontmatter
- Maintain sync with Jira ticket
Output Standards
Present tickets with:
- Clear problem and desired outcome separation
- Concise summary focusing on essentials
- Jira ticket URL for direct access
- Local markdown path for reference
Important Notes
- Ticket number comes from existing file count
- Use
ENG-XXXformat for ticket numbers - Title should be kebab-case
- Always include both Jira URL and local markdown record
- Keep frontmatter consistent across all tickets
- Update Jira via MCP for any changes before finalizing