Gentlybot docs

Your first useful thread.

Ask from Slack or open your project in Gently. Bring a question you would normally ask a teammate; the request, context, and result stay together.

Once your workspace owner connects Slack, invite Gentlybot to your channel. Mention it with a question, or send it a direct message. Name your product and the flow you mean. Attach a screenshot if it helps explain the problem.

This example uses Crosstown, our fictional delivery app. Adapt it to your product:

@gentlybot In Crosstown, what happens when a courier cannot finish a delivery?

Gently posts updates and the answer back in Slack. To ask a follow-up in a channel, reply in the same Slack thread and mention Gentlybot again. It continues the same Gently thread with the conversation context.

@gentlybot What will the customer be told?

If Gently asks a clarifying question, use its answer buttons or Reply action in Slack. You can keep the whole question-and-answer exchange there. Choose Open in Gently when you want to inspect the full thread, try a preview, or explore an artifact together.

Accept your workspace invitation and choose the project you want to work on. Start a new thread from the dashboard. Confirm the project in the composer before sending a request. The thread gets its own isolated environment from the saved project setup; you do not need to install packages or run the app on your laptop.

If there is no project yet, try a starter template or ask your workspace owner to connect the app.

Choose Ask for an answer without code changes. Name the flow or behavior you want to understand, and attach any context Gently would not already have. This example uses Crosstown, our fictional delivery app. Adapt it to your product:

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

You should get an explanation with sources you can inspect. If the answer is too broad, narrow the question in a reply. You do not need to start over.

Open the cited sources. Check that they describe the flow you meant and that the answer distinguishes confirmed behavior from assumptions. Ask for missing context if the evidence is incomplete.

Which rows in the seeded batch are invalid, and why? Show the validation rules and explain how a merchant can correct them today.

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.

A useful answer can be the end of the task. Share the thread with a teammate who needs the same context.

If you want to explore a change, choose Plan and describe the outcome. Add your constraints in the thread. If the change is already clear, you can start directly in Implement.

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

Use these early wireframes to get feedback on potential options. Compare the flow, ask what is confusing, and refine the direction before going deeper into design and code.

For an implemented change, open the running preview, inspect the browser evidence and checks, and review the pull request through your team’s normal process.

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.
Learn how to review the evidence
  • The answer is about the wrong app: check the selected project and name the page or flow in a reply.
  • A source is missing: ask what Gently could access. Your workspace owner may need to connect the repository or tool.
  • The preview is still starting: ask Gently to inspect the environment, diagnose the startup failure, and fix it. Your project owner may need to provide missing access or credentials. Other threads can keep working.
  • The change is incomplete: reply with what you expected and ask for the missing evidence before review.