Convert user needs into structured tickets with acceptance criteria and state transitions.
npx skills add https://github.com/reVrost/dotfiles --skill write-tickets
Please help me install this Agent Skill. Skill: write-tickets Source: https://github.com/reVrost/dotfiles/tree/main/skills/write-tickets Command: npx skills add https://github.com/reVrost/dotfiles --skill write-tickets
Automates the creation of technical tickets by turning user needs into structured tickets with explicit acceptance criteria, state transitions, and implementation guidance.
Provide the user requirements and constraints, and I will generate a complete ticket draft with acceptance criteria, state transitions, and implementation notes.
High-intent search queries and answers about installing and using this skill.
To draft Jira tickets with clear acceptance criteria and state transitions, provide your user requirements and constraints. The system generates a structured ticket template capturing dependencies, risks, and technical notes to guide implementation and verification.
When user-provided details are missing, ticket requirements generate TBD placeholders instead of guessing schemas or error codes. The draft includes an Open Questions section to surface these ambiguities and clarification questions to resolve them before drafting.
Yes, you can use MCP Jira integration to link multi-component work across generated tickets. The workflow supports capturing complex requirements by structuring linked tickets with explicit acceptance criteria and state transitions for coordinated implementation.
The best way to format technical ticket titles and determine ticket type is by applying a standardized title format based on analyzed user needs. The process evaluates requirements to classify the ticket type and capture technical notes for implementation guidance.
Yes, the ticket generation process resolves ambiguous requirements before drafting by asking clarification questions. If users decline to provide missing information, it generates TBD placeholders and surfaces open questions for follow-up rather than guessing schemas.
You should include technical notes and dependencies in structured ticket templates whenever user needs require implementation guidance and verification. Capturing these elements alongside acceptance criteria and state transitions ensures technical tickets have explicit context for developers.
albertoiruruetaDraft and file a Jira ticket with project and issue type selection.
luongldptitRetrieve, analyze, and update Jira tickets via REST API v3 or MCP.
markus41Create Git commits linked to Jira issues with smart commit syntax.
roerohanAutomate Jira ticket creation, updates, status transitions, and searches via CLI.
