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.