Create well-structured Jira issues from code changes, conversations, or requirements. Use when creating issues, bugs, stories, tasks, or when the user wants to track work in Jira. Analyzes context to generate clear titles, descriptions, and appropriate fields.
From jiranpx claudepluginhub ramirez-justin/claude-plugins --plugin jiraThis skill is limited to using the following tools:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.
Expert assistance for creating well-structured, comprehensive Jira issues from any context.
This skill complements the superpowers workflow skills. Use superpowers skills first for process guidance, then this skill for Jira execution:
| Situation | Use Superpowers First | Then Use This Skill |
|---|---|---|
| New feature request | brainstorming → design the feature | Create Story with requirements |
| Complex bug | systematic-debugging → find root cause | Create Bug with findings |
| Multi-step work | writing-plans → break down tasks | Create Epic + linked Stories |
| After completing work | finishing-a-development-branch → verify | Update issue status |
Key principle: Superpowers handles the how (methodology), this plugin handles the where (Jira tracking).
When to use: Something is broken or not working as expected
Required information:
When to use: User-facing feature or capability
Required information:
When to use: Work that doesn't fit other types (refactoring, documentation, DevOps)
Required information:
When to use: Large body of work that contains multiple stories
Required information:
[Type] Brief, clear descriptionUser login fails with special charactersAdd dark mode toggle to settingsRefactor authentication module for testability## Problem
Brief description of what's broken.
## Steps to Reproduce
1. Go to login page
2. Enter email with + character
3. Click submit
## Expected Behavior
User should be able to login with any valid email.
## Actual Behavior
Error: "Invalid email format"
## Environment
- Browser: Chrome 120
- OS: macOS 14
- Version: v2.3.1
## Screenshots/Logs
[Attach if available]
## Impact
Who is affected and how severely?
## Suggested Fix
[Optional] Potential solution or workaround
## User Story
As a [user type]
I want [goal]
So that [benefit]
## Background/Context
Why we're building this feature.
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
## Design/Mockups
[Link to designs if available]
## Technical Notes
- API changes needed
- Database changes
- Third-party integrations
## Out of Scope
What we're NOT doing in this story.
## Objective
What needs to be accomplished.
## Context
Why this work is needed.
## Implementation Details
- Step 1
- Step 2
- Step 3
## Definition of Done
- [ ] Code complete
- [ ] Tests added
- [ ] Documentation updated
- [ ] Reviewed and merged
Note: Priority names vary by Jira instance. Common values include: Blocker, Critical, Major, Minor, Trivial (classic) or Highest, High, Medium, Low, Lowest. Check an existing issue in your project to confirm.
frontend, backend, api, databasemobile, web, desktopperformance, security, accessibilitytechnical-debt, refactoringneeds-design, needs-review, blockedgood-first-issue, help-wantedcustomer-request, urgent, quick-winWhen creating an issue based on code I've written or changes I've detected:
Analyze the change:
Determine issue type:
Extract details:
Generate structured content:
Context: I just helped implement user authentication
Analysis:
Generated Issue:
Title: Implement OAuth 2.0 authentication for user login
Type: Story
Description:
## User Story
As a user
I want to login using OAuth providers (Google, GitHub)
So that I don't need to create another password
## Implementation Details
Added OAuth 2.0 authentication with the following changes:
**Modified Files**:
- `src/auth/auth.js` - OAuth client integration
- `src/components/login.js` - OAuth login buttons
- `src/config/config.js` - OAuth app credentials
**Tests**:
- `tests/auth.test.js` - OAuth flow tests
## Acceptance Criteria
- [x] Google OAuth integration working
- [x] GitHub OAuth integration working
- [x] Error handling for failed OAuth
- [x] Tests added and passing
- [ ] Documentation updated
- [ ] Security review completed
## Security Considerations
- OAuth credentials stored in environment variables
- PKCE flow used for enhanced security
- Token refresh logic implemented
## Next Steps
- Update user documentation
- Security team review
- Deploy to staging for testing
Labels: backend, authentication, security, needs-review
Priority: High
When creating an issue from a discussion:
Identify the core request: What does the user actually want?
Ask clarifying questions if needed:
Structure the information: Use appropriate template
Confirm with user: Show them the issue before creating
When creating issues, consider:
Epic: User Authentication System
├─ Story: Implement OAuth login
│ ├─ Task: Add Google OAuth
│ ├─ Task: Add GitHub OAuth
│ └─ Task: Update login UI
├─ Story: Add password reset flow
└─ Story: Implement 2FA
Before creating an issue, verify:
"Fix login" → "User login fails with OAuth when email contains + character"
"Implement feature" → Include user story, requirements, acceptance criteria
Add clear, testable conditions for completion
Refactoring as Bug → Should be Task
Always set priority based on impact
One issue = one logical unit of work. Split large work into multiple issues.
Me: "I've implemented the user profile feature. Should I create a Jira issue to track this?"
You: "Yes, create a story"
Me: [Analyzes code] "I'll create a story with:
- Title: 'Implement user profile with avatar upload'
- Description includes implementation details from the code
- Acceptance criteria based on what was built
- Labels: frontend, backend, user-management
- Priority: Medium
Create this issue?"
You: "Users report that the app crashes when uploading large files"
Me: "I'll create a bug issue:
## Title
App crashes when uploading files > 10MB
## Description
[Structured bug template with all details]
Should I also search for similar issues first to avoid duplicates?"
If your Jira project has custom templates, I can:
Create multiple related issues at once:
You: "Create issues for the payment integration epic"
Me: "I'll create:
1. Epic: Payment Integration
2. Story: Stripe API integration
3. Story: Payment form UI
4. Story: Transaction history
5. Task: Payment testing in sandbox
Proceed with all 5 issues?"
When you need to create an issue, I will:
/jira-create commandYou: "The authentication module I just wrote should be tracked"
Me: "I'll create a story for this. Let me analyze what you built...
Proposed Issue:
Title: Implement OAuth 2.0 authentication system
Type: Story
Priority: High
Description: [Complete structured description with code context]
Labels: backend, authentication, security
Does this look good? Should I create it?"
You: "Yes"
Me: [Uses /jira-create] "Created PROJ-456: Implement OAuth 2.0 authentication system. Would you like me to add it to your current sprint?"