jira-ticket-writer
Jira Ticket Writer
Quick start
- Identify ticket type (Bug, Story, Task, Spike)
- Ask what the user knows — summary, context, problem or goal
- Fill the template by asking targeted questions for any missing fields
- Present the full draft — iterate until approved
- Optionally create or update via
jira(see jira-cli skill)
Workflow
- Confirm ticket type
- Gather context: what, why, who is affected, what is the expected outcome
- Fill type-specific sections (see TEMPLATES.md)
- Ensure each acceptance criterion is independently testable
- Include a clear definition of done
- Present full draft and iterate on feedback
- Offer to submit via jira cli (jira cli does not work in sandbox mode)
More from miguelez11/skills
atlassian-cli
Interact with Jira and Confluence from the terminal using the Atlassian CLI (acli). Covers CRUD, listing, searching, commenting, and status transitions on Jira work items, plus Confluence space browsing. Use when the user mentions Jira tickets, ADRs, Confluence spaces, sprint boards, or wants to manage Atlassian work items without leaving the terminal.
13git-jira-branch
Switches to the git branch for a Jira ticket. Searches for an existing branch prefixed with the ticket number; if none exists, runs `jiraSwitchToBranch <TICKET>` to create and switch to a new one. Use when the user mentions a Jira ticket number and wants to switch branches, start working on a ticket, check out a ticket branch, or says "switch to TICKET-1234".
6write-a-skill
Add a new agent skill to the MIGUELez11/skills personal GitHub repo. Use when the user wants to create a new workflow, process, or reusable capability and publish it to their skills collection.
6jira-cli
Interact with Jira from the terminal using ankitpokhrel/jira-cli (the `jira` command). Covers issue CRUD, search, sprint management, status transitions, and linking. Use when the user mentions `jira` CLI, wants to create or view Jira issues, list sprints, move tickets, or manage Jira from the terminal without the Atlassian CLI (acli).
5obsidian-prd
Guides the user through a structured PRD creation process via interview, then writes the PRD to an Obsidian vault. Use when user asks to "create a PRD", "add a PRD", "write requirements", "write a spec", or "plan a feature".
3obsidian-tasks
Manages tasks and PRDs in an Obsidian vault via direct file creation. Use when creating task notes, PRD documents, linking tasks to PRDs, or managing blocked-by relationships in an Obsidian Kanban workflow. Triggered by phrases like "create a task", "add a PRD", "link this to a PRD", "mark as blocked by", or "add to kanban".
3