What problem does it solve?
Many Jira tickets lack a structured product and technical specification, making it time-consuming for Program Managers and engineers to convert ticket details into actionable implementation plans. This skill automates the transformation of a Jira ticket's title, description, and metadata into a coherent, review-ready Markdown spec, reducing manual drafting and alignment time.
Core Features & Use Cases
- Automated Ticket Parsing: Extracts ticket ID from plain text or URL and pulls summary, description, status, assignee, project, and linked issues via the Jira MCP tool.
- Structured Spec Generation: Produces a combined Design Doc and Tech Spec following the Connect Spec Doc template, with placeholders where the ticket lacks detail.
- File Output & Integration: Saves the completed Markdown to ./outputs/<TICKET-ID>-spec-doc.md for easy attachment to PRs or sharing with reviewers.
- Use Case: A Program Manager provides a Jira URL and asks for a spec; the skill generates a draft ready for engineering and product review.
Quick Start
Provide a Jira ticket ID or URL and ask the assistant to generate a spec doc for that ticket.