Internal Knowledge Base Builder
Transform scattered tribal knowledge — SOPs, Slack threads, meeting notes, emails — into a structured, searchable knowledge base. Outputs organized articles with categories, tags, and cross-references that any team member can follow.
Dump in everything messy — raw Slack messages, rough notes, half-finished docs. AI is better at extracting structure from chaos than you are at organizing it manually.
How to use this prompt
- Pick your AI model. Choose the tab for Claude, ChatGPT, Gemini or Copilot — each variant is tuned for that model.
- Copy the full prompt. Click Copy Full Prompt to copy the text to your clipboard.
- Paste into your AI tool. Open your chosen model and paste the prompt into a new chat.
- Replace the
[placeholders]. Swap any bracketed fields for your company name, audience, product or tone. - Run and refine. Review the output. If anything is off, ask the AI to tighten tone, length or format.
Prompt Variants by Model
You are a technical writer organizing a small business knowledge base.
<raw_content>
[PASTE EVERYTHING — SOPs, Slack messages, meeting notes, emails, rough docs, bullet points, anything related to...You are a technical writer organizing a small business knowledge base.
<raw_content>
[PASTE EVERYTHING — SOPs, Slack messages, meeting notes, emails, rough docs, bullet points, anything related to this topic]
</raw_content>
<context>
Topic area: [e.g., "How we handle refunds", "Client onboarding process", "Social media publishing workflow"]
Who needs this: [roles that will reference this knowledge]
Knowledge base tool: [Notion / Confluence / Google Docs / Slite / other]
Tone: [formal / casual / somewhere in between]
</context>
Transform this into structured knowledge base content:
1. **Article structure** — organize the raw content into 1-3 articles. For each article:
- Title (clear, searchable)
- Category suggestion
- Tags (5-8 keywords)
- Summary (2-3 sentences)
- Full content with headers, steps, and callouts for important notes
- Related articles (cross-references to other topics mentioned)
2. **Gap identification** — what questions would a reader have that the raw content does NOT answer? List them as "TODO: get answer from [likely person]".
3. **Decision log** — extract any decisions or rules embedded in the raw content and format them as a clear decision table.
4. **Quick reference** — a TL;DR version (under 200 words) for people who just need the answer fast.Act as a technical writer organizing scattered business knowledge into clean documentation.
I am going to give you a messy collection of...Act as a technical writer organizing scattered business knowledge into clean documentation.
I am going to give you a messy collection of content about a topic. Turn it into structured knowledge base articles.
Topic: [WHAT AREA]
Who reads this: [ROLES]
KB tool: [Notion / Confluence / Google Docs / other]
Tone: [formal / casual]
Raw content:
[PASTE EVERYTHING — SOPs, Slack messages, notes, emails, docs]
Create:
1. 1-3 structured articles with: title, category, tags, summary, full content with headers and steps, cross-references
2. Gap list — unanswered questions marked "TODO: ask [person]"
3. Decision log — rules and decisions extracted into a table
4. TL;DR quick reference (under 200 words)Help me organize messy business knowledge into structured documentation.
**Topic:** [WHAT AREA]
**Readers:**...Help me organize messy business knowledge into structured documentation.
**Topic:** [WHAT AREA]
**Readers:** [ROLES]
**KB tool:** [Notion / Confluence / Google Docs]
**Tone:** [formal / casual]
**Raw content:**
[PASTE EVERYTHING]
Create:
1. 1-3 structured articles — title, category, tags, summary, full content, cross-references
2. Knowledge gaps — unanswered questions with "TODO: ask [person]"
3. Decision log table
4. TL;DR quick reference (under 200 words)
If the content references tools or processes, research current best practices to fill obvious gaps.Turn my messy notes into organized knowledge base articles.
Topic:...Turn my messy notes into organized knowledge base articles.
Topic: [WHAT AREA]
Readers: [ROLES]
KB tool: [Notion / Confluence / Google Docs]
Tone: [formal / casual]
Raw content:
[PASTE EVERYTHING]
Create:
1. 1-3 articles with title, category, tags, summary, content, cross-references
2. Gap list with TODO items
3. Decision log table
4. TL;DR (under 200 words)Frequently Asked Questions
What does the Internal Knowledge Base Builder prompt do?
Transform scattered tribal knowledge — SOPs, Slack threads, meeting notes, emails — into a structured, searchable knowledge base. Outputs organized articles with categories, tags, and cross-references that any team member can follow.
Which AI models is this prompt tested on?
This prompt is field-tested on Claude, ChatGPT, Gemini and Copilot. Each model has its own optimized variant above.
Do I need a paid AI account to use this prompt?
No. This prompt is written to run on the free tier of Claude, ChatGPT, Gemini and Copilot. Paid tiers simply give you longer context windows and faster responses.
Can I customize this prompt for my business?
Yes. Any text inside square brackets is a placeholder you replace with your own business details, such as company name, audience, product or tone. You can also ask the AI to adjust format, length or style after the first output.
When was this prompt last verified?
Each model variant above shows its own freshness stamp. AlignAI re-verifies every prompt at least monthly and rebuilds when a major model changes.
Don’t see what you need? tailored to your use case.