5 AI Prompts For Waking Up The Dream You Shelved Years Ago

You are a project archaeologist who helps people reconstruct ideas they shelved years or decades ago. I want to dig up an old dream of mine and describe it clearly enough that I can decide what to do with it now.

What I remember:
- Approximate year I first had this idea: [YEAR]
- The 1-sentence version of what it was: [DESCRIBE]
- What made me excited about it at the time: [DESCRIBE]
- What it would have looked like if I'd finished it: [DESCRIBE]
- Why I stopped (be honest — money, time, skills, fear, family, job, no audience, no idea how, etc.): [LIST]
- What's bringing it back now: [DESCRIBE]
- My age then vs. now: [THEN] / [NOW]
- What's changed in my life since (life stage, finances, free time, health, who depends on me): [DESCRIBE]

Build me a one-page reconstruction:

1. THE CORE IDEA RESTATED in clearer language than I gave you — what it really is, in 2-3 sentences someone outside my head could understand.

2. WHAT I WAS REALLY AFTER. Often the surface idea (write a novel, build a product, start a business) is a stand-in for a deeper want (be heard, be in charge, leave something behind, prove something to a specific person). Name what you think the deeper want actually was. Be specific.

3. WHAT IT WOULD LOOK LIKE FINISHED — the version that would have made me proud if I'd built it. One paragraph.

4. THE LIST OF WHAT STOPPED ME, ranked from biggest blocker to smallest. Be specific. Don't let me get away with "life got in the way."

5. WHAT'S DIFFERENT NOW ABOUT ME (not the world — that's the next prompt) that makes this worth revisiting. Time, money, skills, who depends on me, what I've already proven.

6. THE 1-SENTENCE PITCH I should use when I describe it to one other person this week. The shortest, cleanest version.

This is the starting document. We'll stress-test it in the next prompts.

You are an industry analyst with a long memory. I shelved a project years ago for specific reasons. I want to know what's actually different now, and whether those changes make it worth picking back up — both whether I CAN build it now, AND whether I SHOULD.

The project (one paragraph; use the reconstruction from the earlier prompt if you have it): [DESCRIBE]

The year I originally shelved it: [YEAR]
The current year: 2026

The specific reasons I shelved it (be honest): [LIST]

The industry / market it lives in: [DESCRIBE]

Walk me through what's changed:

1. THE TOOLS GAP. What did it cost in money, time, or specialized skill to build the first version in [YEAR]? What does it cost now? Be specific — name the tools, the typical cost then vs. now, and what's now possible with AI / no-code / cheap SaaS that wasn't possible then.

2. THE DISTRIBUTION GAP. What did reaching the people who'd want this require in [YEAR] — publishers, retailers, agents, ad budgets, sales teams, gatekeepers? What's possible now? Name the direct-to-audience channels that exist today that didn't exist or were embryonic back then.

3. THE EXPERTISE GAP. What specialized expertise was required to make the first version in [YEAR] — coding, legal, financial modeling, design, manufacturing, etc.? Which of those gaps has AI closed? Which are still real?

4. THE DEMAND PICTURE. Has the audience for this idea grown, shrunk, or shifted since [YEAR]? Who is the buyer now vs. then? Has the macro context (aging population, remote work, AI displacement, climate, etc.) made the idea more needed or less needed?

5. THE COMPETITION PICTURE. Who is doing something close to this now? Are they doing it well? Where's the gap they're missing? Or has the space gotten so crowded that the opening I saw in [YEAR] is gone?

6. THE HONEST CAN-I VERDICT. Given all of the above, can someone with my situation actually build a real version of this now? What changed in my favor? What changed against?

7. THE HONEST SHOULD-I VERDICT. Even if I CAN build it, is the world a place where this idea earns its keep? Is there a meaningful audience? Or is this a "yes you could, but the people who would have wanted it have moved on" situation?

8. THE REFRAMED VERSION. If the original idea doesn't quite fit 2026 but the underlying want does, what's the shape of the idea that fits NOW? Sometimes the dream survives but the form changes — a novel becomes a Substack, an invention becomes a Kickstarter prototype, a course becomes a YouTube channel + book. Give me the 2026 version of the dream, not just the original.

Don't soft-pedal. If the gap closed in my favor, say so. If the world moved past the idea, also say so. I'd rather know now.

You are a venture capitalist or experienced operator who has reviewed 1,000+ projects, books, businesses, and inventions and has zero polite incentive to flatter me. I want the unflinching skeptic read on a dream I've been carrying around for years.

The dream (one paragraph; use the reconstruction + reframe from earlier prompts if you have them): [DESCRIBE]

The reframed 2026 version (if different): [DESCRIBE]

My constraints:
- Money I can put into this without hurting my household: $[AMOUNT]
- Hours per week I can realistically work on it: [HOURS]
- Months I'd give it before declaring win or kill: [MONTHS]
- Age and life stage: [AGE], [STAGE — pre-retirement, semi-retired, full retired, sandwich-generation]
- Whether anyone depends on this making money: [YES — who / NO]

Give me the brutal read:

1. THE 3 FATAL FLAWS an experienced operator would spot in 90 seconds. Be specific to THIS dream — no generic "marketing is hard." If you'd pass on this in a pitch, say why.

2. THE 3 REASONS IT COULD ACTUALLY WORK. Only list them if they're real — don't invent them to be nice. If there are fewer than 3, say so.

3. THE BUYER. Who is the actual person who'd pay for this (or read it, or use it)? What are they paying for the closest existing alternative right now? Why would they switch?

4. THE COMPETITION TRUTH. What's already out there that's close enough that this idea has to outrun it? Are the existing options bad enough that the gap is real, or has someone already eaten this lunch?

5. THE CHEAPEST KILLER TEST. The single 7-day test I could run that would either prove the core assumption or kill the dream cleanly. Be concrete — not "do customer interviews" but "draft a one-page sales page and run $50 of ads to it and measure click-through."

6. THE VERDICT. One of these four:
   - PURSUE — the dream survives the skeptic test; do the cheapest killer test immediately
   - REFINE — the core is good but the shape is wrong; here's the smaller version worth testing
   - KILL — the dream doesn't survive the skeptic test; here's why, and you should give yourself permission to stop
   - WAIT — the timing isn't quite right; here's the specific signal to watch for before reviving

Don't humor me. My spouse already does that. I want the read I'd pay for.

You are a maker who specializes in helping people build a quick, visible version of an idea they've been imagining for years — not the polished finished version, the smallest first version they can actually look at. I have a project I want to try building this weekend.

The project (use the reconstruction + reframe + assessment from earlier prompts if you have them): [DESCRIBE]

The version I keep imagining in my head: [DESCRIBE THE FINISHED FORM]

My constraints:
- Hours I have this weekend: [HOURS]
- Money I can spend on tools/services this weekend: $[AMOUNT]
- My existing skills: [LIST]
- What I do NOT know how to do yet (be honest): [LIST]

Build me the weekend version:

1. THE THING I'LL ACTUALLY HAVE AT THE END. Not the finished product. Something I can look at, read, hold, or click. Examples by project type:
   - A book or course → the first chapter + a table of contents (so I can flip through what the finished version would feel like)
   - A business or product → a single landing page that describes it, with a buy or signup button (so I can show 5 people what I mean)
   - An invention → a 3D-rendered image or simple prototype (so I can hold a picture of it in my hand)
   - A piece of software → a working homepage with one feature that actually does something (so I can click it)
   - A community or movement → a one-page manifesto + a way to sign up for updates (so I can collect the first 5 people who want in)

Pick the shape that fits MY project, and tell me what the weekend deliverable is, in one sentence.

2. THE EXACT TOOLS. Name the specific free or cheap tools that will get me there this weekend. Don't say "use AI" — tell me which AI tool, which website builder, which 3D rendering tool, etc. If I'm not technical, the tools must require zero coding.

3. THE HOUR-BY-HOUR PLAN. Break the weekend into 4-8 specific blocks of 1-3 hours each, in order. Each block produces one chunk of the final thing.

4. WHAT THE SECOND PASS LOOKS LIKE. After I see version 1, what's the obvious next improvement? Don't list everything I could improve — just the ONE thing I'll most want to fix in pass 2.

5. WHO I SHOW IT TO. Name the TYPE of person (not a specific name — a type) I should send the weekend version to for the first reaction. The reaction is the data — does it land for them or not? What's the exact question I ask them?

6. HOW I KNOW IT'S GOOD ENOUGH TO MOVE FORWARD. The specific signal — a friend's reaction, a click-through number, a sign-up count — that says "keep going" vs. "rework before continuing."

Be specific about every step. Treat me like someone who's smart but has never built this kind of thing before.

You are a no-BS project planner who specializes in helping people run short, decisive tests on long-shelved ideas. I want a 30-day plan that ends in a clear keep-going-or-stop decision — not a vague "see how it feels."

The project (use everything from earlier prompts if you have it — reconstruction, reframe, assessment verdict, weekend version): [DESCRIBE]

My situation:
- Hours per week I can realistically commit: [HOURS]
- Money I can spend on tools/ads/tests over 30 days: $[AMOUNT]
- What I'm willing to NOT do for 30 days to make space for this (TV, golf, side-scrolling, etc.): [LIST]
- What I am NOT willing to give up (family, sleep, primary job, etc.): [LIST]

Build me the 30-day plan:

1. THE GOAL OF THE 30 DAYS. NOT "build the finished thing." The GOAL is "prove or disprove that this is worth a 6-month commitment." Restate the test in one sentence so I'm clear what's being measured.

2. THE WEEK-BY-WEEK PLAN.
   - Week 1: Build the smallest visible version (the weekend version from the previous prompt, expanded if I have extra time)
   - Week 2: Show it to 10 specific people / put it in front of 100 strangers / make it findable
   - Week 3: Iterate based on what week 2 told me — fix the one thing that was the most common reaction
   - Week 4: Run the decisive test — the cheapest, sharpest measurement that proves or kills the central assumption

3. THE KILL CRITERIA. Spell out the specific numbers or signals that mean STOP at day 30:
   - If [specific measurable signal] is below [number], stop and feel good about stopping
   - If [signal] is between [number] and [number], the answer is "refine and run another 30 days, here's what to refine"
   - If [signal] is above [number], the answer is "this is real; commit to 6 months, and here's what shifts on day 31"

4. THE GO CRITERIA. The same in reverse — what specifically has to be true for me to commit to a 6-month build phase.

5. THE 5-MINUTES-A-DAY MAINTENANCE. The smallest daily ritual that keeps the project from going stale during weeks 2 and 3 when the test is running and there's not much to actively do. One sentence.

6. THE WEEKLY CHECK-IN. The 30-minute Sunday review I run each week. What 3 questions do I ask myself? What 3 numbers do I track?

7. THE LETTER TO MYSELF for day 30. Draft the short letter I send myself on the morning of day 30 that says "here's what you said on day 1, here's the criteria you set, here's how to read the results without lying to yourself." Pre-commit me to actually deciding.

Be brutal about the kill criteria. The whole point is permission to stop cleanly if the data says stop, and permission to commit decisively if the data says go.