メニュー
Use when planning a personal or work trip - lodging, transport, daily plan, packing
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | planning-a-trip |
| description | Use when planning a personal or work trip - lodging, transport, daily plan, packing |
| kind | workflow |
| audience | anyone |
| ai-tools | any |
| complexity | guided |
| time | 20-40 min |
| version | 1.0.0 |
| source | bundled |
Walks you from a vague trip idea to a complete plan: dates, route, lodging, daily structure, and a packing list — without overplanning the things that don't matter.
A trip plan: dates + transport + lodging + day-by-day skeleton + packing checklist + a small "open questions" list.
This is a guided workflow.
Lock the immovable: dates, must-attend events, return-by deadline.
Pick lodging-to-event transport (walk / transit / rental car / rideshare). Book the longest, hardest piece first (long flights, train passes).
Pick lodging by criteria in this order: proximity to anchor events, sleep quality (reviews mention noise / bed), then price. Book.
For each day, write 1-2 anchors (event, meal, sight) and leave the rest open. Overplanning produces brittle trips.
Generate a checklist by category: docs, electronics, clothes (per weather), toiletries, meds, comfort items.
List what you couldn't decide yet (e.g., "decide on dinner spots day-of"). Naming them prevents anxiety.
Return to Stage 2 if lodging quality forces a transport change.
Input: 4 days in Lisbon, mostly rest, one wedding on day 2, travel light.
Output:
Dates: Apr 18-21. Anchor: wedding Sat 4pm. Transport: TAP from JFK Apr 17 night arrival; Uber from airport. Lodging: 4 nights at (5-min walk to wedding venue). Day-by-day:
- Apr 18: arrive, lunch + nap, walking tour (4-7pm)
- Apr 19: wedding (4pm-late)
- Apr 20: late breakfast, beach day
- Apr 21: depart 11am Packing: . Open: dinner Apr 18, beach choice Apr 20.
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"
Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.
Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.
