Agents, skills, and workflows for scrum process management on the OpenShift Edge team.
Edge-Scrum-Laws.md — The authoritative governance document for the OCPEDGE unified scrum. Skills and agents load specific law files from references/laws/ at runtime. It defines:
- Team roster — 18 team members with Jira usernames and per-sprint SP targets
- Jira projects — OCPEDGE, OCPBUGS, OCPSTRAT, USHIFT and their roles
- Issue types and sizing — Story/Spike/Task/Bug (fibonacci SP), Epic/Feature/Initiative (T-shirt sizes)
- Workflow states — per issue type, including the OCPBUGS bug lifecycle
- Sprint policies — 8 SP/person target, churn rules, bug handling
- Bug triage process — severity, priority, target versions, PR title format
- Epic and feature refinement — required fields, description template, SME responsibilities
- Key roles — SME, Epic Assignee, Scrum Master, Team Lead, Payload Manager
mcp-atlassian — Jira integration via the mcp-atlassian container server.
Connects Claude to the Red Hat Jira instance (redhat.atlassian.net) so skills and agents can query issues, sprints, epics, and project metadata without leaving the CLI.
Required environment variables:
Note: There are likely multiple locations that these need to be set (ex: .bashrc, .zshrc, .profile)
| Variable | Description |
|---|---|
JIRA_USERNAME |
Your Red Hat Jira username (email) |
JIRA_API_TOKEN |
Jira API token |
The server runs via Podman (ghcr.io/sooperset/mcp-atlassian:latest) and is configured in .mcp.json.
Analyzes the health of an OCP release cycle. Traverses the full Jira hierarchy — Features/Initiatives (OCPSTRAT) → Epics (OCPEDGE) → Stories/Tasks/Bugs — and produces a structured report with risk assessment, refinement gaps, sprint forecasting, and prioritized actions.
Usage:
/release-health [version] [sprint-range] [bc:branch-cut-sprint]| Example | Description |
|---|---|
/release-health |
Interactive mode — prompts for all parameters |
/release-health 4.19 281-285 bc:285 |
Analyze OCP 4.19, sprints 281–285, branch cut at sprint 285 |
/release-health 4.20 |
Prompts for sprint range |
What it produces:
- Executive Summary — overall release health at a glance
- Release Dashboard — one-line status per Feature/Initiative
- Feature/Initiative Detail — per-feature breakdown with Epic rollups and action items
- Epic Detail — issue-level view for active or at-risk epics
- Risk Register — all risks sorted by severity (schedule, staffing, refinement, blocked work)
- Refinement Backlog — issues needing grooming
- Sprint Forecast — velocity-based projection through branch cut
- Recommended Actions — prioritized, owner-assigned
Output is saved to .reports/release_health_{version}_{YYYY-MM-DD}.md.
See skills/release-health/README.md for full usage details.
Assesses whether the team can deliver planned scope within remaining time. Runs a data-quality gate followed by six planning risk checks — capacity, timeline, assignment, bug load, sizing, and composite progress — to surface risks per person and per feature before they become execution problems.
Usage:
/release-planning [version] [sprint-range] [bc:branch-cut-sprint] [pd:pencils-down-sprint] [--component <component>]| Example | Description |
|---|---|
/release-planning |
Interactive mode — prompts for all parameters |
/release-planning 5.0 287-292 bc:292 |
Analyze OCP 5.0, sprints 287–292, branch cut at 292 |
/release-planning 5.0 287-292 bc:292 pd:291 |
Same, with pencils down at sprint 291 |
/release-planning 5.0 287-292 bc:292 --component TNA |
Filtered to TNA features only |
Pencils down is when all feature code must be merged. Branch cut is when the release branch is created. Feature timeline risk is measured against pencils down. If pd: is omitted, it defaults to the branch cut sprint.
What it produces:
- Data Quality — validates story-level breakdown before running checks
- Capacity — per-person assigned SP vs remaining capacity
- Timeline — per-feature remaining work vs time left
- Assignment — unassigned work and single points of failure
- Bug Load — unassigned Blocker/Critical bugs
- Sizing — T-shirt size vs actual scope mismatches
- Composite Risk — multi-signal risk assessment per feature (LOW/MEDIUM/HIGH)
- Recommendations — actionable per-person, per-feature, and team-level actions
Output is saved to .reports/release_planning_{version}_{YYYY-MM-DD}.md and .reports/release_planning_{version}_{YYYY-MM-DD}.docx.