Your prompts are: - Scattered across chat logs - In personal files nobody can find - Half-remembered, half-lost - Different versions with different people - Undocumented and unversioned
This is normal. Almost every team starts here.
Here's how to get to a proper system in 30 days.
Week 1: Collect
**Day 1-2:** Create a dump folder. Shared location. Call it "prompt-collection-raw."
**Day 3-5:** Hunt for prompts. Check: - AI chat interfaces (export history if possible) - Personal notes and files - Slack/Teams (search for prompt-like content) - Code repos (embedded prompts) - Documentation (if any exists)
Don't organize yet. Just collect.
**Day 6-7:** Ask the team. "Send me any prompts you have. Any format. Doesn't matter if they're good."
People have prompts you don't know about. Ask.
Week 2: Inventory
**Day 8-10:** Create a simple spreadsheet:
| Prompt Name | What it does | Status | Owner | Source | |-------------|--------------|--------|-------|--------| | | | Production/Dev/Experiment/Unknown | | |
Fill it out for every prompt collected.
**Day 11-12:** Identify duplicates. You'll find multiple versions of similar prompts. Note which seems best.
**Day 13-14:** Identify gaps. What prompts do you need but don't have? Note these for later.
Week 3: Organize
**Day 15-17:** Create folder structure:
/prompts /production /development /experimental /archive
Or organize by function: /prompts /code-review /documentation /communication /analysis
Pick what makes sense for your team.
**Day 18-19:** Move prompts to appropriate folders. Use clear naming: function-description-v1.md
**Day 20-21:** For each production prompt, add minimal documentation: - What it does - When to use it - Inputs/variables - Owner
Week 4: Systematize
**Day 22-24:** Set up version control. Options: - Put the prompts folder in Git - Use a prompt management tool - Use a system of record tool
At minimum: Git repo with semantic versions.
**Day 25-26:** Establish workflows: - How are new prompts added? - How are changes made? - What needs review before production? - How is documentation maintained?
Write these down. One page is enough.
**Day 27-28:** Communicate. Tell the team: - Where prompts live - How to find them - How to contribute - Who to ask
**Day 29-30:** Review and adjust. What's working? What's friction? Adjust before habits solidify.
What You'll Have
After 30 days: - All prompts in one place - Organized and findable - Versioned with history - Documented (at least minimally) - Clear process for maintenance
This isn't perfect. But it's infinitely better than chaos.
Maintaining It
The system needs ongoing care: - New prompts get added properly (not to random locations) - Changes follow the workflow - Documentation stays current - Periodic review for staleness
Build these into habits. What gets reinforced persists.
Start Now
Day 1 is whenever you decide it is.
Create the dump folder today. Spend 20 minutes collecting prompts.
You're already ahead of most teams.