jira-url-work-plan

Fetch a Jira issue by URL and generate a Markdown implementation plan.

18|1|Updated Nov 5, 2015
One-click install
npx skills add https://github.com/cristianoliveira/dotfiles --skill jira-url-work-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-url-work-plan
Source: https://github.com/cristianoliveira/dotfiles/tree/main/ai/shared/skills/jira-to-plan
Command: npx skills add https://github.com/cristianoliveira/dotfiles --skill jira-url-work-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jira-cli, and includes scripts (resource) components.

What problem does it solve?

This Skill automates turning a Jira issue into a concrete, executable plan, reducing back-and-forth when starting work from tickets.

Core Features & Use Cases

  • Fetch and analyze Jira issues from a URL using jira-cli to extract essential details (summary, description, acceptance criteria).
  • Clarify & scope by identifying ambiguities and prompting follow-up questions before planning.
  • Deliverable planning by splitting work into commit-sized deliverables with clear scope, acceptance criteria, tests, and a markdown implementation plan.
  • Repeatable workflow producing a shareable plan document that can be reviewed and tracked against milestones.

Quick Start

Provide a Jira issue URL to generate a commit-sized implementation plan. Optionally specify OUTPUT_PATH to write the Markdown plan, e.g., .tmp/plans/PROJ-123.md.

Frequently Asked Questions about jira-url-work-plan

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

FAQPage Schema
How do I turn a Jira issue into a commit-sized implementation plan?

To turn a Jira issue into a commit-sized implementation plan, provide the issue URL. The Skill fetches content via jira-cli, clarifies ambiguous scope, splits work into deliverables with acceptance criteria and tests, and renders a Markdown plan.

How does jira-cli fetch issue content for implementation planning?

Jira-cli fetches issue content by accessing the provided Jira issue URL to extract essential details like summary, description, and acceptance criteria. This data feeds the planning script to generate structured, commit-sized deliverables.

Do I need jira-cli to generate an implementation plan from a Jira URL?

Yes, jira-cli is a required dependency. The Skill uses it to fetch Jira issue content directly from the URL before analyzing scope and generating the markdown implementation plan with commit-sized deliverables.

What's the best way to break down unclear Jira tickets into actionable deliverables?

To break down unclear Jira tickets, the Skill identifies ambiguities and prompts clarifying questions before planning. It then splits the scoped work into actionable, commit-sized deliverables with defined acceptance criteria and tests.

Can I write the generated implementation plan to a specific file path?

Yes, you can specify an OUTPUT_PATH like .tmp/plans/PROJ-123.md. The Skill uses scripts/write_plan.py to render and write the structured markdown implementation plan to that specified location.

What limitations exist when automating Jira issue tracking into deliverables?

Limitations include dependency on jira-cli for content retrieval and the need for clear scope resolution. If Jira issue descriptions lack detail, the Skill must pause to prompt clarifying questions before generating the plan.