smithery.ai

create-jira

Creates WAF JIRA tickets for documentation work using existing ticket infrastructure.

First seen Apr 6, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,348 B
  • docs SUMMARY.md 104 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Create JIRA Skill

Arguments

  • --title / -t: Article title
  • --pillar / -p: 1 Optimize Systems, 2 Secure Systems, 3 Define and Automate Processes, 4 Design Resilient Systems
  • --products: Comma-separated HashiCorp products
  • --quarter / -q: 1-6 (2026Q1-2027Q2)
  • --product-line: 1 Security, 2 IPL, 3 Runtime, 4 WAF
  • --pillar-label: optimizesystems, securesystems, defineandautomatesystems, designresilient_systems
  • --interactive / -i: Guided prompts for all fields (recommended first use)
  • --description-file / -d: Path to pre-written description file
  • --from-section: Create ticket from a /new-section created document
  • --preview: Preview ticket without creating

Ticket creation process

  1. Guidance: Define requirements, target personas, scope
  2. Description file: Create from template at jiratickets/descriptiontemplate
  3. Validation: All required fields filled, links provided, example documents included
  4. Submission: Calls jiratickets/scripts/createjira.sh, converts to ADF format, returns ticket URL
  5. Output: Issue key (e.g., WAF-497) and URL

Description file template

Target personas:

Decision-makers (CTOs, architects, staff engineers):
- [Strategic value and business impact]
- [How it fits broader architecture]

Implementers (DevOps, platform engineers):
- [Technical details and how to implement]
- [Links to hands-on resources]

Requirements:
- [Key concepts to explain]
- [Specific examples needed]

Scope:
- IN: [What's included]
- OUT: [What's excluded]

References:
- `/templates/AGENTS.md`
- `/templates/doc-templates/DOCUMENT_TEMPLATE.md`

Example documents:
- [Link to similar WAF doc]
- [Link to similar WAF doc]

Acceptance criteria:
- All requirements included in final doc
- GitHub PR merged and validated

Links:
- Document URL: https://developer.hashicorp.com/well-architected-framework/...
- Design document: [Google doc URL]

Prerequisites

export JIRA_EMAIL="[email protected]"
export JIRA_API_TOKEN="your-api-token"

Requires: python3, jq, curl.