Trunk
Epic + tasks + PRs +
PRD + signals · one object.
A delta owns the whole change — the motivating signal, the PRD, the design, the approval, the typed code slices, the PRs, the deploy, the post-ship metric. Six phases. Six gates. One number: #7.
| ID | Team | Title | Priority | Progress | Size |
|---|---|---|---|---|---|
#7 |
Cart |
Epic
Add You may also like empty state to /cart
6 slices · 2 PRs · conflict with #5
|
High |
In Progress
2/6 slices merged
|
L |
#6 |
Checkout |
Epic
Rename Checkout → Place order
Copy + token change · all slices green
|
Medium |
Review
5/5 slices · ready to merge
|
S |
#5 |
Shop |
Epic
Refactor StoreHeader → semantic <header>
Conflict with #7 — both touch StoreHeader
|
High |
Blocked
1 conflict · needs resolve
|
M |
#3 |
Account |
Experiment
Skip login for returning customers
Journey change · adds cookie-based fast-path
|
Medium |
In Progress
2/3 slices merged
|
M |
#2 |
Shop |
Bug
Fix /product 500 on out-of-stock
Repairs broken node from Journey graph
|
Urgent |
In Progress
hotfix · 1 PR open
|
S |
#1 |
Shop |
Epic
Draft /wishlist screen
Missing screen · implied by product-detail flow
|
Low |
Draft
not yet scoped
|
XL |
Not a review chain. Six review chains, one per phase.
Each phase has an owner, an artifact, and a gate. Sign what your role sees — not what someone stitched into a giant single-review approval.
Pin the motivating signal.
Write the PRD on the delta.
Styles · Components · Pages · Journey.
Cost + team split before Code.
Typed slices become real PRs.
Preview → staging → prod.
One slice. One PR. One reviewer.
Under Code, every delta breaks into typed slices — Frontend, Backend, CI/CD, Misc, Backlog. Each slice raises one Pull Request against your repo. CI runs. Review happens. Nothing merges without its gate.
- ✓Slice types are configurable — add Docs, Localise, whatever you need.
- ✓Route to humans by role. Assignment follows the phase gate.
- ✓Real PRs on GitHub / GitLab / Bitbucket. No vendor blob.
Shipped deltas write your changelog.
Every closed delta has a summary, an owner, and a validating signal. Trunk stitches them into a release-notes view — one entry per delta, grouped by week. No handmade changelog files. Publish to a public page or keep it internal.
- ✓Grouped by week · filtered by delta type
- ✓Links back to the delta, the PR, the signal
- ✓Publish public or keep internal — same source
Merges are visual. Because designs are.
When two branches touch the same primitive, Trunk shows a 3-way visual diff — base, yours, theirs — with an auto-merged result you can tune. Same idea as Git, at the design layer.
Deltas are the spine.
Everything else in Trunk hangs off a delta. Signals wire to it. Documentation anchors to it. Flags belong to it. Journey redraws for it.