valent-pipeline 0.2.15 → 0.2.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -42,7 +42,21 @@ From the source document, identify each story and extract:
|
|
|
42
42
|
| Dependencies | No | Which stories must ship before this one can start (`depends_on`) |
|
|
43
43
|
| Optional inputs | No | UX spec, architecture notes, scenario outlines if mentioned |
|
|
44
44
|
|
|
45
|
-
**Priority assignment
|
|
45
|
+
**Priority assignment — E2E-first ordering:**
|
|
46
|
+
|
|
47
|
+
The goal is to get working end-to-end slices as early as possible, not to finish one epic before starting the next.
|
|
48
|
+
|
|
49
|
+
1. **Identify vertical slices.** Scan all stories across all epics and group them into vertical slices — sets of stories that together produce an end-to-end testable path through the system. What counts as "end-to-end" depends on project type:
|
|
50
|
+
- **backend-api**: request entry point → business logic → data persistence → response
|
|
51
|
+
- **fullstack-web**: UI interaction → API call → backend processing → UI display
|
|
52
|
+
- **data-pipeline**: data ingestion → transformation → output/storage
|
|
53
|
+
Each slice should be the smallest set of stories that delivers a complete path. Prefer simpler stories (fewest ACs, fewest dependencies) for the first slice.
|
|
54
|
+
|
|
55
|
+
2. **Order slices by value.** Rank slices so the most foundational or highest-value E2E path comes first. Later slices may share stories with earlier ones — don't duplicate, just note the dependency.
|
|
56
|
+
|
|
57
|
+
3. **Assign priorities slice-first.** Assign priorities 1 through K to the first slice (ordered by dependency chain), K+1 through M to the second slice, and so on. Stories that appear in multiple slices keep the priority from their earliest slice.
|
|
58
|
+
|
|
59
|
+
4. **Fill in the rest.** Assign remaining priorities to stories that don't belong to any vertical slice, in normal epic order (story sequence within epic, epics in document order). Cross-epic dependencies use `depends_on`.
|
|
46
60
|
|
|
47
61
|
**Dependency detection:** Look for:
|
|
48
62
|
- Explicit "depends on" or "requires" references
|
|
@@ -52,18 +66,27 @@ From the source document, identify each story and extract:
|
|
|
52
66
|
|
|
53
67
|
## Step 4: Present Summary for Approval
|
|
54
68
|
|
|
55
|
-
Before writing any files, show the user:
|
|
69
|
+
Before writing any files, show the user with the vertical slice separated:
|
|
56
70
|
|
|
57
71
|
```
|
|
58
|
-
|
|
72
|
+
Vertical Slice 1 (E2E path: {description}):
|
|
73
|
+
{STORY-ID}: {title} [priority: 1] {depends_on if any}
|
|
74
|
+
{STORY-ID}: {title} [priority: 2] {depends_on if any}
|
|
75
|
+
|
|
76
|
+
Vertical Slice 2 (E2E path: {description}):
|
|
59
77
|
{STORY-ID}: {title} [priority: {N}] {depends_on if any}
|
|
60
|
-
{STORY-ID}: {title} [priority: {N}]
|
|
61
78
|
...
|
|
62
79
|
|
|
63
|
-
|
|
64
|
-
|
|
80
|
+
Remaining Backlog:
|
|
81
|
+
Epic: {EPIC-NAME}
|
|
82
|
+
{STORY-ID}: {title} [priority: {N}] {depends_on if any}
|
|
83
|
+
{STORY-ID}: {title} [priority: {N}]
|
|
84
|
+
...
|
|
85
|
+
|
|
86
|
+
Epic: {EPIC-NAME}
|
|
87
|
+
...
|
|
65
88
|
|
|
66
|
-
Total: {N} stories across {M} epics
|
|
89
|
+
Total: {N} stories across {M} epics ({K} in {S} vertical slices)
|
|
67
90
|
Dependencies: {list any depends_on relationships}
|
|
68
91
|
```
|
|
69
92
|
|