Epic Goal*

The Epic tracks the execution of OTA team's openshift engineering Q4 AI goals.

Why is this important? (mandatory)

It helps us distribute team execution to achieve our organization's strategic goals on AI adoption. By integrating AI into our workflow, we can focus our talents on critical, complex technical challenges.

The context and importance has been provided in Q4 AI Goals: Required Actions for OpenShift ICs and Managers/Staff Engineers

Scenarios (mandatory) 

Provide details for user scenarios including actions to be performed, platform specifications, and user personas.  

Dependencies (internal and external) (mandatory)

• Claude Code
• Getting access to the openshift-eng org via https://devservices.dpp.openshift.com/support/github_access_request/ to contribute slash commands to https://github.com/openshift-eng/ai-helpers 

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development 
• QE 

Acceptance Criteria (optional)

• AGENTS.md for each repo
• Team context in sheet.
• Coding standards documented
• Pre-review slash command
• Smoke tests

Done - Checklist (mandatory)

Satisfying the acceptance Criteria