Plan a trip through several cities and pause before booking
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and plan a trip through several cities and pause before booking.
LLMPrompt
Prompt
Copied 0
Plan a trip for [number of travellers]. Treat these as fixed and never change them: we leave [home city] on [departure date] and are back by [return date]; the cities, in order, are [city (nights), city (nights), city (nights)]; the total budget for transport and hotels is [amount and currency]. If any of these cannot work, pause and check with me instead of choosing other dates or cities yourself. My preferences: [for example, rail for any journey shorter than five hours, hotels with a rating of at least 8 and free cancellation and within walking distance of the centre, no departures before 9 AM]. 1. Before searching, ask me anything you need to know. 2. Draft a plan for each day. For every leg, give two options with the operator, local departure and arrival times, duration, price, plus a link to the listing and the time you looked. For every city, give two hotels with the nightly price, the rating and star class exactly as the site shows them, the cancellation terms and the distance to [the area I care about]. Do not round or guess; write "not shown" for anything you could not see. 3. Check the plan: time needed to get between stations and hotels, arrival times against check-in times, and whether [any sights I named] are open on the days we are there. Then STOP: present the plan and wait until I have picked one choice per leg and one hotel per night. 4. For every choice I make, go to its booking page and complete it, stopping before you reach payment, with the travellers, dates and room I agreed to. Before handing over, read me what that page shows for travellers, dates, the room, the full price and the refund policy. Whenever you reach a sign-in, a CAPTCHA, a form asking for personal details or a payment screen, pause and let me take over. Never type in card details, and only pick a rate without refunds if I say so. 5. Once I have paid for a booking, record it and its confirmation number in a single itinerary document.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/plan-a-multi-city-trip-and-stop-before-booking - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "plan-a-multi-city-trip-and-stop-before-booking",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}