Skip to content
TriedPrompts

More in Trip planning & itineraries.

Plan a Zion trip with Claude Code docs when a storm floods the Narrows

PartialEvidence: Described by posterPosted Last checked

Claude Code built eight Zion trip docs for Aaron Fulkerson; the Narrows hike could not happen after a storm, but backups worked.

How to use this

  1. Tap Copy prompt.
  2. Open the tool the case used (or a similar one) and paste the prompt; results may differ from the original.
  3. Paste it into the message box.
  4. Send it, then read the answer before acting on it.
New to this? What's a prompt?

A prompt is the message you send to the AI tool. Copy the one on this page, put your own details where it asks, and read the answer before you act on it.

Prompt

Recreated prompt

The source didn't share its exact prompt, so we wrote one from what it describes. The result shown is the source's, not ours.

What the prompt labels mean

The person didn't share their exact words, so we wrote this from what they described. We haven't tested it, and they didn't use this exact version.

Plan a backcountry trip to Zion for me and my son. We care about history, archaeology, geology and peculiar characters. Build interlinked documents for itinerary and logistics, ranked hikes with backups, river-flow conditions against the Narrows closure threshold, emergency facts, food, checklists, deep geology/history and campfire stories. Save them for offline use.

Try this in:

Sends the Recreated prompt shown above. ChatGPT and Grok open with it filled in, and ChatGPT may send it straight away. Gemini and Claude open empty, so we copy the prompt for you to paste. Every button also copies it.

The source used Claude Code, which can take actions on your computer or in a browser. These are general chat tools, so results may differ, and a normal chat may only give you a plan.

Opens in a new tab. We don't see what you send.

These links are only a shortcut. We're not affiliated with OpenAI, Google, Anthropic or xAI, and your results may not match the source.

Optional stronger version

Our rewrite with extra checks. The poster didn't test it.

Before you start, ask me 1–3 short questions about the details below and wait for my answers. Once I've answered, confirm the plan in one line and run the whole task start to finish.

Goal: Build an offline Zion trip library with ranked backups if weather kills the headline hike.

Questions to ask me first:
- Who is going, and what permits or campsites are already booked?
- What topics should the reading docs cover?
- What river-flow threshold closes your key canyon hike?

Inputs (fill in or confirm):
- Travelers: [NAMES / AGES]
- Dates and permits: [DETAILS]
- Interests: [GEOLOGY / HISTORY / STORIES]
- Closure threshold: [CFS / RULE]

Rules:
- Produce separate linked documents, not one giant dump.
- Rank hikes with researched backups per day.
- Track conditions against the closure threshold.
- Keep history docs regional so they still work if routes change.

Checkpoint: Show the document outline and hike ranking method before writing full prose.

If you get stuck: If a permit detail is missing, ask me rather than inventing confirmation numbers.

Verify before you finish: Every primary hike has at least one backup and a conditions note.

Output: An Obsidian-ready set of trip docs plus a short how-to-read-offline note.

Done when: We can hike an alternate plan without losing the educational materials.

AI tool

Claude Code

Outcome

Aaron Fulkerson spent two sessions with Claude Code (a local setup called Exo) planning a Zion trip with son Roe that originally included a top-down Narrows hike with permits. Claude Code produced eight interlinked Obsidian documents: day-by-day itinerary, stack-ranked hikes with backups, conditions vs a 120 CFS Narrows closure threshold, quick facts, food guide, checklists, plus deep geology/history and campfire stories. A storm on day two flooded the rivers, so they skipped the Narrows. The ranked backups paid off: LaVerkin Creek was the third-ranked backup, and they hiked Hop Valley with twenty-plus flooded crossings, then explored Buckskin Gulch. The region history docs still applied to the landscape they actually walked.

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Known limitations

PartialThe source says it only partly worked, or had a significant problem a person had to deal with.

What went wrong: Claude Code's plan and backups were useful, but a storm flooded the Narrows so the original hike could not happen.

Source

Posted
by Aaron Fulkerson
Last checked
Method:
How we verify

https://aaronfulkerson.com/2026/04/13/what-claude-code-built-for-my-son-and-me/

Context: Partial because the original Narrows plan was canceled by weather. Self-reported.

More in Trip planning & itineraries