OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

Leverage the Claude flow to generate the zstream test epic and enable the Jenkins MCP server to trigger the Jenkins jobs for ACM zstream test.

Why is this important?

...

Scenarios

Generate the zstream test epic and break down the tasks

Enable the jenkins MCP server to help to trigger the Jenkins jobs for ACM zstream test

Have func to do the result generated by Jenkins CI 

Integrate Jira PAT into the CI pipeline to post the Job results into the Jira Epic/Task

Acceptance Criteria

z-stream test epic is generated with detailed testing information

1. testing matrix, ACM version, Hub/Managed OCP version
2. testing platform, Cloud(AWS, Azure, etc), Vmware
3. testing coverage, component coverage by Jenkins bug analysis

break down the tasks

1. generate the tesitng tasks, fresh install, z and y version upgrade, stage, post-publish, advisory review
2. generate the bug verification task to each component squad

Have func to do the result generated by Jenkins CI 

1. Send the Jenkins result to Slack/Email
2. the notification list the pass/failure cases information

Integrate Jira PAT into the CI pipeline to post the Job results into the Jira Epic/Task

1. the pipeline results can be automatically updated into the Jira Epic/Task
2. the results list the passed/failure cases information

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)