From edge-scrum
Use when creating a new Epic in Jira for the OpenShift Edge team — enforces team conventions for required fields, description template, sizing, and parent linkage from Edge Scrum Laws
How this skill is triggered — by the user, by Claude, or both
Slash command
/edge-scrum:create-epicThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are creating a new Epic in Jira for the OpenShift Edge team. All conventions come from the Edge Scrum Laws. Read `plugins/edge-scrum/references/laws/` files listed under "Create Epic" in `plugins/edge-scrum/references/Edge-Scrum-Laws.md` before proceeding.
You are creating a new Epic in Jira for the OpenShift Edge team. All conventions come from the Edge Scrum Laws. Read plugins/edge-scrum/references/laws/ files listed under "Create Epic" in plugins/edge-scrum/references/Edge-Scrum-Laws.md before proceeding.
projects: [OCPEDGE, USHIFT]
issue_type: Epic
fields:
parent_link: customfield_10018 # Epic → Feature/Initiative
qa_contact: customfield_10470 # User picker
docs_approver: customfield_10473 # User picker (Doc Contact)
t_shirt_size: customfield_10795 # T-shirt size for Epics (XS/S/M/L/XL)
Use one of these exactly:
MicroShiftTwo Node with ArbiterTwo Node with FencingSNOLogical Volume Manager StorageBandwidth ReductionTopology TransitionWork outside these workstreams uses a scoped label instead of a component.
| Size | Expected Duration |
|---|---|
| XS | ~1 sprint (consider using a Story instead) |
| S | ~2 sprints |
| M | ~3 sprints |
| L | ~4 sprints |
| XL | ~5 sprints (likely too big; split or create a Feature/Initiative) |
The user may provide arguments: $ARGUMENTS
Arguments can include any combination of:
--parent OCPSTRAT-XXX — parent Feature/Initiative key--project OCPEDGE or --project USHIFT — target project--component "Component Name" — workstream component--size M — T-shirt size (XS/S/M/L/XL)--assignee username — epic assignee--qa username — QA Contact--docs username — Doc ContactRead these law files from plugins/edge-scrum/references/laws/:
01-jira-projects.md — valid components (workstreams) and labels04-jira-epics.md — Epic conventions and T-shirt sizing06-jira-fields.md — custom field IDs07-workflow-states.md — valid Epic states13-roles.md — role assignments (QA Contact, Doc Contact)14-agent-conventions.md — Jira conventions for agentsThe Laws are authoritative. When this skill and the Laws conflict, the Laws win.
Parse any provided arguments. Use AskUserQuestion for every missing value — do not assume defaults for description fields:
OCPEDGE or USHIFTunassigned_jira if no QE needed (do not leave blank)unassigned_jira if no docs needed (do not leave blank)If a parent key is provided, verify it exists using jira_get_issue. Warn if the parent is in "Closed" or "Done" state.
Before creating, confirm:
unassigned_jira)If validation fails, report the issue and ask the user to correct it.
Build the description from the template:
## Goal
{goal}
## Dependencies
{dependencies}
## Completion Criteria
{completion_criteria}
Create the issue using jira_create_issue with:
ocpedge-plan]customfield_10470): provided QA contactcustomfield_10473): provided doc contactcustomfield_10795): provided size (XS/S/M/L/XL)customfield_10018): parent key (if provided)Report to the user:
https://redhat.atlassian.net/browse/{KEY}MicroShift.jira_create_issue.ocpedge-plan label is added by default to include the epic in the Jira Plan.Creates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.
npx claudepluginhub openshift-eng/edge-tooling --plugin edge-scrum