From aai-pm-jira
Provides Jira wiki markup syntax and templates for bug reports, user stories, technical tasks, and epics to create structured tickets.
npx claudepluginhub bradtaylorsf/alphaagent-teamThis skill uses the workspace's default tool permissions.
This skill provides patterns and templates for creating high-quality Jira tickets.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
This skill provides patterns and templates for creating high-quality Jira tickets.
Jira uses its own wiki markup, not Markdown:
h1. Heading 1
h2. Heading 2
h3. Heading 3
*bold*
_italic_
-strikethrough-
+underline+
{{monospace}}
* Bullet point
** Nested bullet
# Numbered list
## Nested numbered
{code:java}
// Code here
{code}
{code:javascript}
// JavaScript code
{code}
{noformat}
Plain text, no formatting
{noformat}
[Link text|http://example.com]
[PROJ-123] - links to ticket
||Header 1||Header 2||Header 3||
|Cell 1|Cell 2|Cell 3|
|Cell 4|Cell 5|Cell 6|
{panel:title=Panel Title}
Panel content here
{panel}
{info}
Information callout
{info}
{warning}
Warning callout
{warning}
h2. Bug Summary
[One sentence description of the bug]
h2. Environment
* *Browser/OS*: [e.g., Chrome 120 / macOS]
* *Environment*: [Production/Staging/Development]
* *Version*: [App version if applicable]
h2. Steps to Reproduce
# Step 1
# Step 2
# Step 3
h2. Expected Behavior
[What should happen]
h2. Actual Behavior
[What actually happens]
h2. Screenshots/Logs
[Attach or describe]
h2. Additional Context
[Any other relevant information]
h2. User Story
*As a* [type of user]
*I want* [goal/desire]
*So that* [benefit/value]
h2. Context
[Background on why this is needed]
h2. Acceptance Criteria
* Given [context]
* When [action]
* Then [expected result]
h2. Out of Scope
* [What this story does NOT include]
h2. Technical Notes
* [Any technical considerations]
* [Related files or systems]
h2. Design
[Link to designs or describe UI requirements]
h2. Objective
[Clear statement of what needs to be done]
h2. Background
[Why this task is needed]
h2. Requirements
* Requirement 1
* Requirement 2
* Requirement 3
h2. Technical Approach
[High-level approach, not implementation details]
h2. Files to Modify
* {{path/to/file1.ts}}
* {{path/to/file2.ts}}
h2. Testing
* Unit tests: [What to test]
* Integration tests: [What to test]
h2. Definition of Done
* [ ] Code complete
* [ ] Tests passing
* [ ] Code reviewed
* [ ] Documentation updated
h2. Epic Overview
[High-level description of the initiative]
h2. Goals
* Goal 1
* Goal 2
* Goal 3
h2. Success Metrics
||Metric||Target||Current||
|[Metric 1]|[Target]|[Baseline]|
|[Metric 2]|[Target]|[Baseline]|
h2. Scope
h3. In Scope
* Feature 1
* Feature 2
h3. Out of Scope
* Feature X
* Feature Y
h2. Dependencies
* Dependency 1 [PROJ-XXX]
* Dependency 2
h2. Timeline
||Phase||Target Date||
|Design|[Date]|
|Development|[Date]|
|Testing|[Date]|
|Release|[Date]|
h2. Stories
[Link child stories here as they're created]
Good: "Add email notification when order ships" Bad: "Email feature"
| Priority | When to Use |
|---|---|
| Blocker | System down, data loss |
| Critical | Major feature broken |
| High | Significant impact |
| Medium | Moderate impact |
| Low | Nice to have |
tech-debt, security, performance, documentation| Points | Complexity |
|---|---|
| 1 | Trivial change |
| 2 | Small, well-understood |
| 3 | Medium, some unknowns |
| 5 | Large, multiple parts |
| 8 | Very large, significant unknowns |
| 13 | Epic-sized, consider splitting |
// POST /rest/api/3/issue
{
"fields": {
"project": { "key": "PROJ" },
"issuetype": { "name": "Story" },
"summary": "Add email notifications for shipped orders",
"description": {
"type": "doc",
"version": 1,
"content": [/* ADF content */]
},
"priority": { "name": "Medium" },
"labels": ["notifications", "email"],
"components": [{ "name": "Backend" }]
}
}
// POST /rest/api/3/issue/{issueKey}/comment
{
"body": {
"type": "doc",
"version": 1,
"content": [/* ADF content */]
}
}
Note: Newer Jira API uses Atlassian Document Format (ADF) for rich text instead of wiki markup.