Playbooks by team

Gentlybot earns its keep differently for each function. These are concrete plays — with example prompts — you can adapt to your own app, tickets, and channels.

PMs and program leads

Answer feasibility yourself, turn requests into reviewable plans, and hand engineering something scoped instead of a paragraph in a doc.

Scope feasibility before a decision

Ask

A customer wants per-team billing. Is our current billing model account-scoped or team-scoped today, and what would it take to support both? Cite the files.

Turn a request into a plan

Plan

Draft a plan for weekly scheduled report emails — scope, the surfaces it touches, risks, and test ideas — so I can share it with engineering before we commit.

Prototype to pressure-test an idea

Implement

Build a rough version of the report-scheduling UI in a sandbox so I can click through it in our design review. Record the flow.

Product and brand design

See changes in the real app instead of a mockup, check states you can’t easily prototype, and get accessibility feedback grounded in the actual DOM.

See a change in context

Implement

Tighten the spacing and type scale on the settings page to match our tokens in app/assets/css/main.css. Show me before and after in a sandbox.

Exercise every state

Implement

Screenshot the invoice table in its loading, empty, error, and long-content states so I can review the whole set.

Check accessibility for real

Ask

Audit the checkout form against WCAG AA — contrast, focus order, labels, target sizes — against the live rendered page, not the design.

Test and quality

Reproduce reports against the real stack, generate test plans from the code, and get repro recordings you can attach to a ticket.

Reproduce a report

Implement

Reproduce SUP-482 — empty CSV on export — in a sandbox, record it, and tell me the exact steps that trigger it.

Generate a test plan

Ask

List the edge cases worth testing for the new export flow, including failure modes in the worker, and note which ones we don’t cover today.

Add the missing coverage

Implement

Add tests for the export empty-state and timeout cases, run them, and open a PR.

Developers and leads

Offload the well-understood work, get architecture answers with citations, and let Gentlybot handle the toil while your team keeps review and merge.

Understand an unfamiliar area

Ask

Trace how a webhook from Stripe flows through the system — receipt, verification, the jobs it enqueues, and where it writes. Cite each hop.

Hand off a scoped change

Implement

Migrate the reports endpoint from the deprecated pagination helper to the cursor-based one, matching how #298 did it. Keep the tests green and open a PR.

Investigate a production error

Ask

Here’s a stack trace from Sentry (pasted). Where does this throw, what conditions cause it, and what’s the smallest safe fix?

Marketing and sales

Get grounded product answers, verify claims before they go in a deck, and stand up a tailored demo without pulling an engineer off their work.

Answer a prospect question

Ask

Does the product support SCIM user provisioning today? If not, what’s the closest thing we do offer? Give me a customer-safe answer with caveats.

Verify a claim

Ask

We want to say “exports handle millions of rows.” What’s the real limit in the code, and is that claim safe to make?

Tailor a demo

Implement

Seed a sandbox with data that looks like a logistics customer so I can run a live demo for tomorrow’s call.

CS and support

Tell a bug from expected behavior, prepare account follow-ups with proof, and check whether a fix has shipped — without escalating every ticket.

Bug or expected?

Ask

A customer says invites aren’t sending. Screenshot attached. Is this a bug or a configuration issue on their side, and what should I tell them?

Reproduce with proof

Implement

Reproduce the invite issue in a sandbox and record it, so I can attach the video to the ticket and the escalation.

Check fix status

Ask

Has the fix for the timezone bug in scheduled reports shipped? Which release, and does it cover the case this customer hit?

Ops, admins, internal tools

Wire recurring triage and reporting into automations, and fix internal glue as reviewed work instead of one-off scripts nobody remembers.

Automate triage

Auto

When a data-sync bug lands in #bug-triage, reproduce it, find the likely cause, and reply in the thread with findings.

Schedule a report

Auto

Every Monday at 9:00, summarize last week’s merged PRs by area and post the digest to #eng-updates.

Fix an internal tool

Implement

The admin CSV importer chokes on quoted commas. Fix the parser, add a test with a nasty sample row, and open a PR.

Make these prompts your own

These are starting points — the real ones name your files, your customers, and your channels. The guide on writing great prompts covers how to sharpen any of them.

Writing great prompts