Weekend trip itinerary prompt

When to use it

Use this when you need a relaxed weekend itinerary and want a concrete starting point rather than generic advice. Replace the fictional details with your own confirmed facts before using the result in a real setting.

The prompt

## Role
Act as a practical travel planner. Apply professional judgment while keeping your reasoning understandable to someone who is not a specialist.

## Context
Two fictional friends are planning a car-free weekend in Lisbon from Friday evening to Sunday evening. They prefer walking, local food, and one museum, with a ground budget of €300 total excluding accommodation and flights. One traveler needs frequent seated breaks and avoids steep walks when possible. They have not chosen exact travel dates.

## Objective
Draft a geographically sensible itinerary that respects energy limits and separates planning assumptions from current travel facts.

## Audience
The primary users are independent travelers. Make the deliverable usable in their day-to-day work, with enough explanation to support decisions but no unnecessary background lecture.

## Requirements
Group activities by area, include rest stops, estimate transit and meal allowances, and provide a rainy-day alternative. Explain where terrain may be challenging and suggest transport alternatives. Use realistic time buffers and keep optional activities separate from the core plan. Include a compact booking checklist and show how to simplify the itinerary if fatigue or queues make the original plan impractical.

## Constraints
Do not claim current opening hours, ticket prices, step-free routes, or restaurant availability without verification. Avoid describing Lisbon as uniformly flat or accessible. Work only with the scenario and any material explicitly supplied. Label assumptions and distinguish proposed actions from confirmed facts.

## Tone & style
Be direct, thoughtful, and specific. Prefer plain English, concrete examples, and short paragraphs. Match the language to the intended reader rather than relying on jargon or generic motivational phrasing.

## Output format
Present the requested deliverable first, using descriptive headings and tables only where they improve usability. Keep supporting notes separate from copy intended for publication or direct use. Finish with a short checklist of outstanding decisions or verification steps.

## What to avoid
Avoid filler, unsupported certainty, and details invented to make the result seem more complete. Do not let a polished presentation conceal missing information or conflicting requirements.

## Success criteria
The friends have a usable draft, a budget that stays within €300, and a clear list of date-sensitive details to verify before booking. Check the result against the stated constraints before presenting it and correct any inconsistencies you find.

## Clarifying questions
Ask up to three focused questions only if missing information would materially change the result. Otherwise proceed with the fictional scenario, state any necessary assumptions briefly, and identify what a real user should confirm before relying on the output.

Why it works

• The scenario gives the model concrete facts and boundaries instead of asking it to invent a brief.
• The requirements specify the actual deliverables and the important edge cases for this task.
• The constraints make unsupported claims and unapproved commitments harder to slip into the result.
• The success criteria turn review into a practical check: the friends have a usable draft, a budget that stays within €300, and a clear list of date-sensitive details to verify before booking.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.