Weekly status roll-ups are compiled by hand, every week.
Use cases
For operations
Wire the triggers once. The triage, reports, and glue run themselves.
When a bug lands in Jira, Gently triages it automatically. The 9am report posts itself. The “tiny” internal script ships as a PR — without the engineering bottleneck.
Gently handles the project setup. Each thread gets its own isolated environment and running preview, so you can work without local installs or waiting for a shared environment to be fixed.
Triggers fire prompts from Jira, GitHub, Slack, or a schedule — no babysitting.
Inbound issues get triaged automatically, with a comment back to the source.
Internal scripts ship as reviewed, versioned PRs — not tribal knowledge.
The request and the working result
Test a successful and a failed delivery.
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.
Crosstown is a fictional delivery app. This capture comes from actual work in Gently.
Small automations sit in the eng backlog for months.
Runbooks live in one engineer’s head and break when they’re out.
What you can do
Operations, in one workspace.
Triggers from anywhere
Jira, GitHub, Slack, or cron fire a saved prompt — wire it once.
Auto-triage
Inbound issues are reproduced and explained, with a comment back to the source.
Scheduled digests
The weekly support-inbox sweep and “what shipped” reports post themselves.
Scripts as PRs
Internal glue gets reviewed, versioned, and out of one engineer’s head.
Jira triggers Cron schedules Auto-triage Implement → PR Fan-out MCP
Gently for every team
Product managers
Feasibility → an approved plan → a working prototype + PR.
Designers
Wireframe to align, live preview to verify, PR to ship the polish.
QA & testers
Test plans you can run, video proof, and an automated PR test gate.
Engineering
Implement to a verified PR, then auto-fix CI and address review comments.
Give operations a safe way to work with the product.
Start with questions. Grow into plans, previews, tests, and pull requests when your team is ready.
Request access