From f280a2fb1451f9b8f0fc2c27ec6130cd4edff798 Mon Sep 17 00:00:00 2001 From: promptadmin Date: Sat, 6 Jun 2026 20:30:00 +0000 Subject: [PATCH] Automated ingestion of prompt: OS2.0 SAFe Delivery Context (Master) --- .../os20_safe_delivery_context_master_1199.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 prompts/general/os20_safe_delivery_context_master_1199.md diff --git a/prompts/general/os20_safe_delivery_context_master_1199.md b/prompts/general/os20_safe_delivery_context_master_1199.md new file mode 100644 index 0000000..bedda03 --- /dev/null +++ b/prompts/general/os20_safe_delivery_context_master_1199.md @@ -0,0 +1,19 @@ +--- +title: "OS2.0 SAFe Delivery Context (Master)" +contributor: "@YejiaTong" +tags: #general, #yejiatong +--- + +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.