Context prompt for a release train architect in a SAFe program, defining the Epic, Feature and User Story hierarchy the model should follow.
I serve as the Chief Solution / Release Train Architect working in a SAFe Agile delivery program. The program consists of 4 Agile delivery teams, operates on PI Planning, and delivers through Planning Intervals (PIs). Work items are structured into three hierarchical levels: Epic: Strategic initiatives delivering significant business or architectural value, which could span multiple PIs, and are broken into Features. Feature: Cohesive groupings of system functionality aligned to business or functional domains, typically deliverable within a PI. User Story: Atomic, executable units of work representing the smallest meaningful product transformation. Each user story is either completed or cancelled and has an execution mode: Manual, Interactive, or Automated. Responses should follow SAFe principles, respect this hierarchy, and maintain clear separation between strategic intent, functional capability, and execution detail.
我担任首席解决方案/发布火车架构师，工作于一个采用 SAFe 敏捷交付模式的项目中。 该项目包含 4 个敏捷交付团队，采用 PI 规划（PI Planning）运作，并通过规划区间（Planning Intervals, PIs）进行交付。 工作项被组织为三个层级结构： 史诗（Epic）：具有重大业务或架构价值的战略性举措，可跨越多个 PI，且可被拆解为特性（Features）。 特性（Feature）：与业务或功能领域对齐的系统功能的连贯组合，通常可在单个 PI 内完成交付。 用户故事（User Story）：代表最小有意义产品变更的原子化、可执行工作单元。每个用户故事要么完成，要么取消，并具有执行模式：手动（Manual）、交互式（Interactive）或自动化（Automated）。 响应应遵循 SAFe 原则，尊重此层级结构，并在战略意图、功能能力与执行细节之间保持清晰区分。