jira-spec-doc

Generate Markdown product and technical spec documents from Jira ticket IDs or URLs.

3|7|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill jira-spec-doc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-spec-doc
Source: https://github.com/dimagi/dimagi-claude-workflows/tree/main/plugins/connect-tech/skills/jira-spec-doc
Command: npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill jira-spec-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about jira-spec-doc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a spec document from a Jira ticket automatically?▼

Generating a spec document from a Jira ticket requires providing the ticket ID or URL to the assistant. The skill extracts ticket details using the Jira MCP tool and populates a Markdown template to produce a review-ready spec.

What is the process for converting a Jira ticket into a technical specification?▼

Converting a Jira ticket into a technical specification involves parsing the ticket ID, fetching summary and metadata via the Jira MCP tool, and populating a structured Markdown template with placeholders for missing details.

Can I use a Jira URL to create a product specification for Connect projects?▼

Yes, you can use a Jira URL to create a product specification for Connect projects. The skill parses the URL to extract the ticket ID and automatically drafts a combined design doc and tech spec.

Do I need a specific Jira cloud ID to pull ticket fields for documentation?▼

Yes, pulling ticket fields for documentation requires a specific Jira cloud ID. The skill is configured to use a predefined cloud ID via the Jira MCP tool to fetch the necessary ticket data for spec generation.

What happens to Jira ticket fields that lack detail in the generated spec?▼

Jira ticket fields that lack detail are populated with placeholders in the generated spec. This ensures the Markdown document maintains a structured format for product and technical review.

Where are the completed Markdown spec files saved after generation?▼

Completed Markdown spec files are saved locally to the ./outputs/ directory. The file is named using the ticket ID, resulting in a path like ./outputs/<TICKET-ID>-spec-doc.md for easy sharing.