What problem does it solve? Converting meeting action items, spec user stories, and ad-hoc task lists into well-formed Jira tickets is repetitive and error-prone. This Skill parses unstructured input, enriches it with type, priority, assignee, and story points, and creates tickets via the Jira REST API only after user confirmation. ## Core Features & Use Cases - Multi-source parsing: Accepts meeting action items, user stories from spec files, free-text lists, and sprint planning output. - Automatic field inference: Infers ticket type (Bug, Task, Story) from keywords, maps assignees to a team directory, and estimates story points. - Structured user story format: Enforces a title pattern plus Problem Statement, Objective, and optional Acceptance Criteria sections for Story tickets. - Confirmation workflow: Presents a ticket table with totals for review before creating anything in Jira. - Use Case: After a sprint planning meeting, paste the action items and ask to create tickets; review the proposed table of stories, bugs, and tasks, then approve to push them to the backlog. ## Quick Start Ask the assistant to create Jira tickets from your meeting action items or user story list and confirm the proposed ticket table.
