Skip to content

Latest commit

 

History

History
39 lines (29 loc) · 1.24 KB

File metadata and controls

39 lines (29 loc) · 1.24 KB
type Epic
project RHAIENG
fields
issuetype components customfield_12313240 customfield_12311141
name
Epic
name
Tooling Experience
name
Tooling Experience

Business Objective

[State the overarching goal, customer need, or framework capability being delivered. e.g., Deliver an E2E agentic example using CrewAI with tool-calling on RHOAI.]

Technical Approach

[High-level architecture or technical plan drafted by the Feature Shepherd. Include target framework, deployment pattern (local + RHOAI), and any POC links.]

External Dependencies

[List any cross-team dependencies, upstream framework blockers, or RHOAI platform requirements. If none, state "None".]

Epic Acceptance Criteria

  • E2E example is functional locally and deployed on RHOAI
  • Documentation and README are complete and reviewed
  • CI/CD pipeline passes for the example

Shepherd Breakdown Checklist

  • Epic is broken down into properly sized Stories, Tasks, and Spikes.
  • Child tickets meet the Definition of Ready (clear intent, AC defined, pointed).
  • Work is delegated across the team to build shared expertise and prevent knowledge silos.