sanguo/prompts.chat
3
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Add prompt: OS2.0 SAFe Delivery Context (Master)

Browse Source
This commit is contained in:
YejiaTong
2026-02-12 12:13:12 +03:00
parent 28aa5675c4
commit df349d9b07
2 changed files with 38 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PROMPTS.md
+25
View File
@@ -73391,3 +73391,28 @@ Consider using shapes and typography that convey a futuristic and user-friendly
</details>
<details>
<summary><strong>OS2.0 SAFe Delivery Context (Master)</strong></summary>
## OS2.0 SAFe Delivery Context (Master)
Contributed by [@YejiaTong](https://github.com/YejiaTong)
```md
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.
```
</details>
prompts.csv
+13
View File
@@ -58949,3 +58949,16 @@ Reimagined Logo for Google,"Act as a Logo Designer. You are tasked with creating
- Be versatile for use in various digital and print formats.
Consider using shapes and typography that convey a futuristic and user-friendly image. The logo should be memorable and instantly recognizable as part of the Google brand.",FALSE,TEXT,vksdrive24@gmail.com
OS2.0 SAFe Delivery Context (Master),"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.",FALSE,TEXT,YejiaTong
Can't render this file because it is too large.