Every “is this possible?” pings an engineer and costs a context switch.
Use cases
For product managers
Scope it, plan it, prototype it — and hand engineering a real PR.
Ask feasibility against the real code, turn it into a plan you approve, and watch Gently build a working prototype on a live preview — without interrupting an engineer.
Feasibility answers grounded in real code and git history — in minutes.
A plan you approve before any code, naming the systems it touches.
A clickable prototype on a live URL plus a PR engineering reviews.
One real thread, start to finish
Scope and prototype “scheduled report emails”
northwind / web
D
DanaAsk
How does our report export work today, and where would per-team “scheduled email” delivery hook in?
Worked for 9s · 6 tools
Exports are generated on demand; nothing is scheduled yet. The natural seam:
- Today — report rendering already lives in a reusable service
- Missing — a scheduler + an email sender — no schema change needed
- Effort — small-to-medium; reuses the existing job queue
References
lib/reports/render.ts:64
lib/jobs/queue.ts:21
D
DanaPlan
Plan a “scheduled report email” feature: pick a report, a cadence, and recipients.
Scheduled report emails
Awaiting approval- Add a schedule model (report, cadence, recipients)
- Cron job renders + emails on cadence
- Settings UI: “Schedule report” dialog
- Tests for weekly/monthly cadences
ApproveEditBuild here
You approve the plan — or hand it to engineering as-is. Here, Dana approves and builds.
D
DanaImplement
Approved — build it.
lint
test
commit
push
pr
pr-274.northwind.sandbox.gentlybot.dev/settings/reports
Live Add scheduled report emails#274
open 12/12 passed
Dana drops the open items into Jira straight from the thread — written from the real plan, with the PR linked.
D
DanaAsk
How does our report export work today, and where would per-team “scheduled email” delivery hook in?
Worked for 9s · 6 tools
Exports are generated on demand; nothing is scheduled yet. The natural seam:
- Today — report rendering already lives in a reusable service
- Missing — a scheduler + an email sender — no schema change needed
- Effort — small-to-medium; reuses the existing job queue
References
lib/reports/render.ts:64
lib/jobs/queue.ts:21
Ask, plan, or build anything…Auto
Specs drift from reality — they’re written from memory, not the code.
Ideas stall in the backlog waiting on eng bandwidth to even prototype.
What you can do
Product managers, in one workspace.
Feasibility, instantly
Ask whether something is possible; get an answer that cites the real files.
Plans you approve
Plan mode drafts the approach and the systems involved — approve, edit, or hand off.
Working prototypes
Build to a live preview URL stakeholders can click, before anything merges.
Grounded tickets
Turn the thread into Jira tickets written from the real scope, PR linked.
Ask mode Plan mode Live preview Implement → PR Jira
Gently for every team
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.
Operations
Jira/cron triggers, auto-triage, and internal scripts as PRs.
Give product managers 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