PASTE THIS ENTIRE PROMPT INTO A NEW CLAUDE CONVERSATION
It will ask you a few questions, then generate your project documentation. Easy peasy.
======================================================================

Hey Claude! I need your help creating documentation for a project I'm building. You're going to ask me a few questions, then SET UP three documents for me. I don't have to figure out what goes where -- you handle the structure. I just answer the questions.

Here's the plan:

1. FIRST, ask me these questions ONE AT A TIME (wait for my answer before moving on):
   - What are you building? (An app, a bot, a website, a workflow -- describe it like you're telling a friend)
   - Who is it for, and what problem does it solve for them?
   - What are the 3-5 things this project absolutely MUST be able to do? (Think: "This thing must be able to ___." Concrete, testable stuff -- not vibes.)

2. AFTER I answer all three, generate THREE documents for me:

   **DOCUMENT 1: PROJECT SPECS**
   - Project name and one-sentence description
   - Who it's for (audience)
   - What it does (features, in plain English)
   - How it works (the basic flow, no jargon)
   - What tools/platforms it uses (if I mentioned any)

   **DOCUMENT 2: MUST-DOS**
   A numbered checklist of things the project MUST be able to do, written as testable behaviors. Each one should finish the sentence: "This project must be able to ___."
   Include the ones I gave you, plus suggest 2-3 more I probably need but didn't think of.

   **DOCUMENT 3: CHANGELOG TEMPLATE**
   A pre-formatted changelog I can copy and start using immediately. Structure it like this:
   ```
   # [PROJECT NAME] CHANGELOG

   ## [Date]
   ### What changed
   -

   ### Why
   -

   ### What to know for next session
   -
   ```
   Include a note at the top that says: "Update this every time you make changes. Claude has the memory of a goldfish -- this is your artificial memory. Without it, every conversation starts from scratch."

3. AFTER generating all three, ask me: "Want to tweak anything, or are these ready to save?"

IMPORTANT RULES:
- Ask me ONE question at a time. Don't dump them all at once.
- Keep it warm and encouraging. I might be new to this.
- Use plain English. No jargon, no developer-speak.
- If I say "I don't know" to something, help me figure it out. Don't skip it.
- Add a little goblin-mine energy to the vibe. We're digging up gold here, not filling out tax forms.