How teams ship

From a blocked delivery to a product improvement.

Crosstown is a fictional same-day delivery app for Toronto shops. We used it in real Gently threads to answer delivery questions, sketch courier availability, build a feature across repositories, and test the delivery journey. These captures show the work in the product; the changes remain in their sandbox branches for review.

01 · Support

Customer support asks

A courier cannot complete a delivery. Support needs to explain the next step and what the customer will hear.

Task prompt

A courier accepted a route but cannot finish a delivery. What should they do, and what will the customer be told?

Result: Gently found the courier’s failed-delivery flow and the customer email. The merchant handles another delivery; the app does not promise an automatic retry.
02 · Design

Product and design asks

Couriers need a simple way to choose the days they can work. The team wants to compare two options.

Task prompt

Sketch two simple ways for couriers to set which days they are available to work.

Read the full task prompt

Sketch two simple ways for couriers to set which days they are available to work. Follow-up: Show both as compact, rough sketches side by side so we can compare them in one view. Follow-up: Keep the two options side by side in a 650px-wide thread, with the whole sketch under 450px tall. Follow-up: The sketch clips the bottom controls. Make both cards fit fully without internal scrolling.

Result: Gently sketches a recurring weekly schedule and a date-by-date option for comparing how couriers choose their working days.
03 · Engineering

Engineering asks

Couriers need to set when they can work, so operations can offer each route to someone available that day.

Task prompt

Let couriers set their availability, and only offer routes to couriers available that day.

Result: Couriers choose their available days, and route offers respect that schedule. The day toggle persisted after a browser reload; all 64 API tests passed after review fixes.
04 · QA

QA asks

A courier accepts a route, delivers one order, and cannot deliver another. QA needs to check what happens next.

Task prompt

Test that a courier can accept a route, deliver an order, and mark another delivery as failed. Check the customer emails too.

Read the full task prompt

Test that a courier can accept a route, deliver an order, and mark another delivery as failed. Check the customer emails too. Follow-up: Re-test accepting a route, delivering one order, and marking another delivery failed in the browser. Use demo orders with customer email addresses and check both emails. Follow-up: Summarize the completed browser checks and the two verified emails in a short checklist.

Result: Gently completed the courier flow in the browser and verified both the delivery confirmation and failed-delivery email in Mailpit.
05 · Another feature

Engineering asks

Customers need a link they can open to check their delivery and see the proof photo.

Task prompt

Build a delivery tracking page with ETA and proof photo, linked from the customer’s delivery email.

Read the full task prompt

Build a delivery tracking page with ETA and proof photo, linked from the customer’s delivery email. Follow-up: The tracking link opens the marketing site’s 404 page in Preview. Fix the routing so the email link opens the tracking page.

Result: The customer’s email link opens a private tracking page with delivery status and a progress timeline. The operator verified the rendered page after Gently fixed the cross-app route mapping.

of pull requests opened from threads get merged

median from first prompt to merged PR

threads where Gently checked its own work in a real browser

threads are questions and research, not code changes

people prompting, from engineering to sales

Production usage across our first teams, May–August 2026.

Ask about the behavior, explore a design, or request an implementation. Keep the evidence and follow-up work in Gently so your team can review it together.

Request access