Process
One example.
Three checkpoints.
One human in the loop.
Mira grooms it. Niko builds it. Nova reviews it. Lenny merges it. One pattern among several. The loop adapts to the engagement — the checkpoints don't.
A typical flow
Story in.
Merged code out.
- 01HMNLennyStory filed
A ticket lands in Linear. Priority set. Intent captured. The queue has a new item.
- 02BAMiraEpics & stories
Mira drafts epics and stories. Acceptance criteria written. Edge cases documented.
- 03HMNLennyStory approved
Lenny reviews AC, checks scope alignment, maps dependencies across stories. Parallel work identified before anyone builds. Nothing moves without this gate.
CHK · 01 - 04DEVNikoBuild
Niko branches from the feature branch, builds against AC. PR opened with structured description — what changed, why, how it was verified.
- 05QANovaQA review
Nova checks for merge conflicts first. Then runs the diff against acceptance criteria. Approved and merged to the feature branch, or Requested Changes back to Niko.
CHK · 02 - 06DEVNikoAddress feedback
Nova files a change request on the PR. Niko responds with the fix. The thread is the record — every request and response documented in context.
- 07HMNLennyFeature review & merge
Lenny reviews the full feature — not just individual diffs. Manual testing in browser. Anything that doesn't meet the bar routes back through the loop.
CHK · 03
One story
STORY-214,
/ start to merge.
STORY-214 · Solterra Workshop
Cart — add and manage
Owner Niko Westin AGENT·A01
Reviewer Mira Solis AGENT·A02
Approver Lenny Reed Human
Acceptance criteria
- AddToCart component renders on product pages — cart count updates immediately on add
- Product image component includes AddToCart overlay — click adds item without page navigation
- Cart page renders all line items with product image, name, unit price, and quantity
- Per-item +/− controls update quantity and recalculate subtotal in real time
- Remove button deletes line item — subtotal and count update immediately
- Cart page displays subtotal, item count, product detail, and empty state when cart is cleared
QA Review
- All 6 AC verified across add, update, and remove flows with 3 test products
- Subtotal recalculates correctly across mixed qty and price combinations
- Empty state confirmed after removing last item — prompt to continue shopping renders
- No console errors or TypeScript warnings on any path tested
Status: Approved
PR Review
feat/IRN-214-cart
+312 −14 across 9 files
“Cart interactions are tight. The image overlay is a nice touch. This is the core commerce layer — ship it.” — Lenny Reed
> orchestrator.spawn("niko")
✓ context loaded · 19.7k tok
✓ tools: [github, linear, fs]
> linear.read(story=IRN-214)
✓ 6 AC items · client: Solterra Workshop · status: in progress
> agent.plan(goal="cart — add and manage")
↳ step 1/4 AddToCart component + cart state
↳ step 2/4 product image overlay · click to add
↳ step 3/4 cart page · line items · qty +/− · remove
↳ step 4/4 subtotal · product detail · empty state
> agent.implement() ...........
✓ AddToCart + image overlay · cart state updates ✓
✓ qty +/− recalculates subtotal in real time ✓
✓ remove item · count + subtotal update · empty state ✓
> yarn build
✓ 0 errors · 0 warnings · all 6 AC verified
> git commit -m "[IRN-214] feat: cart — add and manage"
> gh pr create → handoff to Mira
PR · OPENStart
Ready to run the process?

