resources-to-jira

Convert PRDs and technical designs into code-validated Jira Epics and micro-stories.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/dicarsmtz/product-engineering-kit --skill resources-to-jira-dicarsmtz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resources-to-jira
Source: https://github.com/dicarsmtz/product-engineering-kit/tree/main/plugins/product-engineering/skills/resources-to-jira
Command: npx skills add https://github.com/dicarsmtz/product-engineering-kit --skill resources-to-jira-dicarsmtz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning product requirements documents and technical designs into Jira tickets often produces bloated, stale, or inaccurate stories that reference outdated file paths and assumptions. This Skill validates plans against the actual codebase and generates lean, dependency-ordered Epics and micro-stories ready for engineering execution. ## Core Features & Use Cases - Codebase Validation: Inspects the current codebase to verify file paths, base classes, and helper functions before writing any ticket, eliminating stale design-doc assumptions. - Lean Ticket Generation: Produces Epics under 150 words and Stories under 100 words with mandatory User/Business Value statements, phase prefixes, and acceptance criteria checklists. - Jira Field Automation: Converts acceptance criteria into ADF JSON via a helper script and populates BlueFlame BFAI custom fields like Product Area and Testing Needed. - Use Case: A product engineer pastes a PRD for a new API integration and receives a structured Epic plus Phase 0/1/2 stories with validated file paths, dependency links, and correctly formatted Jira custom fields. ## Quick Start Use the resources-to-jira skill to validate this PRD against the codebase and create a Jira Epic with phased micro-stories.

Frequently Asked Questions about resources-to-jira

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

FAQPage Schema
How do I convert a PRD into Jira tickets?

Provide the PRD or design doc and the Skill validates file paths against the codebase, then generates an Epic under 150 words plus micro-stories under 100 words each. Stories are grouped into Phase 0 Foundation, Phase 1 MVP, and Phase 2 Endgame with dependency links.

How to create Jira acceptance criteria in ADF format?

Run the scripts/adf_acceptance.py helper with your criteria lines as arguments or via stdin. It outputs a Jira ADF bullet list JSON document ready to send to the acceptance criteria custom field (customfield_10132).

Does this work with Jira custom fields like Product Area?

Yes, it populates BlueFlame BFAI custom fields including Product Area (customfield_10134) and Testing Needed (customfield_10095) with the correct option IDs. The references file lists common option IDs, but you should query field metadata first since availability varies by issue type.

Why should tickets be validated against the codebase first?

Design docs often contain stale assumptions about file paths, base classes, and helper functions. Validating against the actual codebase ensures stories reference real modules and follow existing patterns, preventing implementation blockers.

What are the limitations of this ticket generation approach?

It enforces strict word caps (100 words per story) and an MVP-only scope, deferring features like A/B testing and complex roles to an Out of Scope section. It is tailored to the BlueFlame BFAI Jira project, so custom field IDs may not transfer to other Jira instances.