What problem does it solve?
Creating Jira Epics manually is slow and error-prone because teams must consistently apply Edge Scrum Laws for required fields, descriptions, sizing, components, and parent linkage.
Core Features & Use Cases
- Edge Scrum Law–driven Jira Epics: Reads authoritative conventions (workstreams, labels, field IDs, states, roles) and uses them to structure the Epic so it fits team standards.
- Guided, validated data capture: Collects missing inputs (summary, project, component/workstream, parent Feature/Initiative key, size, assignees, QA/Doc contacts, and description sections) and validates allowed values before creation.
- Creates the Epic in the correct Jira shape: Builds the templated description with Goal, Dependencies, and Completion Criteria, then creates the Epic with the required fields, components, and
ocpedge-plan label.
Quick Start
Create a new Edge Epic by asking for a summary, project, workstream component, parent Feature/Initiative key (optional), T-shirt size, assignee, QA contact, Doc contact, and the Goal/Dependencies/Completion Criteria, then confirm everything before the skill calls Jira to create the issue.
