Jira Ticket Writer
Transform requirements into structured JIRA tickets with acceptance criteria and estimates
What You Can Do
You can rapidly convert unstructured requirements into standardized, actionable JIRA tickets that your team can immediately work with. The skill generates searchable titles, testable acceptance criteria in Given/When/Then format, logical subtasks that break work into completable units, and story point estimates aligned to your team's velocity. This ensures consistency across tickets and reduces back-and-forth clarification during sprint planning and execution.
Features
Example Output
Input: Raw requirement: "Users should be able to search for products by category and filter results by price range."
Output:
Title: Enable product search by category with price range filtering
Acceptance Criteria:
- Given a user is on the product catalog page, When they select a category from the dropdown, Then the results filter to show only products in that category
- Given filtered results are displayed, When the user adjusts the price range slider, Then results update in real-time to show only products within the selected range
- Given search results are filtered, When the user clears filters, Then all products are displayed again
Subtasks:
- Implement category filter UI component (3 points)
- Build price range slider with real-time filtering (5 points)
- Write integration tests for filter combinations (3 points)
- Update product search API endpoint (5 points)
Story Points: 13
Definition of Done: Code reviewed ✓ | Tests passing ✓ | Product approved ✓ | Documentation updated ✓
What's Included
- SKILL.md: Complete instruction set for the JIRA Ticket Writer
- Ticket Template: Pre-structured format with fields for title, acceptance criteria, subtasks, and estimates
- Gherkin Format Guide: Reference for writing testable Given/When/Then scenarios
- Definition of Done Checklist: Customizable template to ensure tickets meet your team's standards
- Story Point Estimation Framework: Guidelines for calibrating estimates to your team's velocity
Who It's For
- Project Managers — standardizing ticket quality and ensuring clarity before sprint planning
- Product Owners — translating user feedback and feature requests into actionable work items
- Scrum Masters — facilitating backlog refinement and ensuring tickets meet Definition of Done
- Engineering Leads — establishing consistent ticket structure across distributed teams
- Business Analysts — documenting requirements in a format developers can immediately implement
Best For
- Converting user stories and feature requests into structured JIRA tickets
- Writing acceptance criteria in testable Gherkin format
- Breaking down large epics into estimated, manageable stories
- Documenting and standardizing bug reports with reproduction steps
- Preparing backlog for refinement sessions with clear, actionable work items
- Ensuring new tickets comply with your team's Definition of Done before assignment
You might also like
You can systematically analyze complex financial transactions, communications, and documents to identify prosecution weaknesses and develop credible alternative defense narratives. This skill helps you organize massive volumes of evidence, map communication timelines, and spot inconsistencies in the prosecution's theory that can support reasonable doubt arguments.
by jzocb
This skill analyzes EB-5 investor visa cases for regulatory compliance, identifies potential risks across investment structure and source of funds documentation, and generates USCIS-compliant narrative frameworks and case strategy documents. You'll receive detailed case assessments with risk ratings, recommended documentation strategies, and structured narratives that position your clients' applications for approval.
by jzocb
This skill helps you design complete Chapter 11 restructuring plans, including waterfall analysis, creditor classification, and recovery projections. You can generate professional disclosure statements with detailed financial assumptions, feasibility analysis, and recovery calculations that withstand court scrutiny. The skill analyzes operational assumptions, debt scenarios, and creditor groups to produce plan documents that maximize creditor recoveries while maintaining operational continuity.
by jzocb
Assess beneficiary eligibility against family-based sponsorship requirements, generate comprehensive case analyses with supporting documentation strategies, and draft petition narratives and RFE response frameworks. You'll identify optimal petition categories, calculate timeline projections, and flag compliance issues—transforming complex family cases into strategic, well-documented petitions ready for USCIS.
by jzocb
This skill helps healthcare compliance officers and fraud prevention specialists analyze regulatory requirements, identify compliance gaps, and evaluate anti-fraud controls. You'll generate detailed audit findings with specific remediation recommendations, assess policy effectiveness against federal fraud and abuse standards, and document compliance risks in audit-ready formats.
by jzocb
You can submit an IRS position, proposed adjustment, or audit report, and this skill will identify legal weaknesses, inconsistencies with precedent, and procedural issues. It structures persuasive counter-arguments based on statutory interpretation, case law authority, and factual analysis—helping you build a stronger negotiating position or appeal brief.
by jzocb
Systematically evaluate whether your business information qualifies as a trade secret under the Uniform Trade Secrets Act (UTSA) and Defend Trade Secrets Act (DTSA), then generate a customized framework of protective measures required to maintain legal protection. You'll receive detailed analysis of misappropriation risk, documentation protocols, and remedies available under applicable law.
by jzocb
You can take raw business needs, stakeholder feedback, and problem statements and transform them into professionally structured requirements specifications. The skill decomposes ambiguous requests into detailed functional and non-functional requirements, organizes them as user stories with acceptance criteria, and prepares them for development handoff. This bridges the gap between business stakeholders and development teams while ensuring clarity on what "done" looks like.
by vigorx777