Threads by function

See what your team can do with the same app.

Real Gently threads, one fictional delivery product. Crosstown connects a merchant portal, operations dashboard, courier app, Rails API, and background jobs. Each thread gets an isolated environment from the same project setup. Product, design, support, and engineering can work in parallel without installing the app on their own machines. See their questions, wireframes, implementation, and testing below.

Product lifecycle

Product lifecycle
View full product managers thread

Product manager prompts

Merchants need a spreadsheet of the orders they can fix.

Task prompt

Let merchants download a CSV of the orders that need attention, including what is wrong with each order.

Result: The CSV contains three flagged orders and their issue descriptions. Request specs check its contents and merchant access.
Product lifecycle
View full designers thread

Designer prompts

Make the file the first step, while keeping the sample and existing validation.

Task prompt

Build the direct-upload design with my annotation and Priya’s feedback. Keep the sample download, and test the empty and file-selected states on desktop and mobile.

Result: Jennifer builds the direction agreed with Priya. The date appears after choosing a file; sample downloads stay within reach.
Product lifecycle
View full qa & testers thread

QA tester prompts

Verify both the filtered state and the way back.

Task prompt

Fix it. Add regression coverage, then verify in the browser that only the three problem orders remain and switching back restores all ten.

Result: Two regression tests pass. The browser confirms ten orders become three problem orders, then restores all ten.
Product lifecycle
View full engineering thread

Product manager prompts

A PM builds a way for couriers to choose when they work, so operations can offer routes to someone available that day.

Task prompt

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

Result: A working feature in the existing app: couriers choose their available days, and route offers respect that schedule. Ready for the team to try and review.

Go-to-market

Go-to-market

Engineering prompts

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.
Go-to-market

Sales prompts

A shop wants to know whether its customers can track deliveries and see proof of delivery.

Task prompt

Can customers track their delivery and see a proof photo in Crosstown today?

Read the full task prompt

Can customers track their delivery and see a proof photo in Crosstown today? Follow-up: Give me the short version I can use before a sales demo.

Result: Gently confirmed that proof photos can arrive by email, while a customer tracking page and ETA updates are still missing from the baseline app.
Go-to-market
View full operations thread

QA prompts

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.

Customer teams

Customer teams

Customer success prompts

The team wants to understand merchant adoption and help each shop get more value from Crosstown.

Task prompt

Compare merchant usage in Crosstown. Who should customer success follow up with, and how can we help them get more value?

Read the full task prompt

Compare merchant usage in Crosstown. Who should customer success follow up with, and how can we help them get more value? Follow-up: Show the usage comparison and the two follow-up priorities in a compact summary. Keep the demo-data caveat.

Result: Gently compared the demo merchants’ upload and order counts, then suggested upload-quality help for Bloom & Stem and repeat-use onboarding for Corner Loaf.
Customer teams

Customer support prompts

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.
Use cases

Try the same kinds of requests on your own product: ask about current behavior, explore a change, or take it through implementation and review.

PMs, design, QA, engineering
Product lifecycle

Paste a screenshot, ask for wireframe directions, react in the thread, then tell the same thread to build the one you picked — the wireframe is the spec.

Example prompt

“Here’s a screenshot of the settings page — the tab order feels off. Give me a few wireframe options I can react to.”

What comes back
  • Wireframe directions in-thread
  • Share link for feedback
  • “Implement option 2” handoff
  • Reviewed PR
Marketing and sales
Go-to-market

Sales watches the funnel with standing threads on live account data; marketing ships site and positioning updates as reviewed pull requests.

Example prompt

“Which trials look shaky this week? Tag the account executive on each one with the reason.”

What comes back
  • Standing weekly thread
  • AEs tagged in Slack
  • Reasons from live account data
  • Adjustable in plain language
CS and support
Customer teams

Ask account and billing questions from Slack, have the agent reproduce reported bugs in the real app, and hand back replies backed by screenshots.

Example prompt

“A customer says their export is missing fields. Is that a bug? Can you try to reproduce it?”

What comes back
  • Bug-or-expected answer
  • Repro screenshots as proof
  • Drafted customer reply
  • Fix PR from the same thread
Ops, admins, internal tools
Operations

The Monday-morning sweeps — reading the support inbox, triaging product requests, watching releases for docs drift — run on a schedule, each as a thread you can open and audit.

Example prompt

“Every week, read the last 7 days of support conversations and report the top product requests.”

What comes back
  • Scheduled weekly thread
  • Requests triaged and tallied
  • Proposals wireframed for top pains
  • Fan-out into fix threads

The safest rollout is narrow: choose one team, one complex app workflow, and one kind of request. Expand once the collaboration and review loop feels good.

Request access