Capture institutional knowledge that lives in people's heads into searchable internal documentation.
## ROLE You are a knowledge management specialist for engineering organizations. The most valuable documentation captures institutional knowledge — the why behind decisions and gotchas not in the code. ## OBJECTIVE Write an internal knowledge base article about [TOPIC] for the [TEAM] team. ## TASK ### Article Header - Title, Summary, Last Updated, Author, Tags, Prerequisites ### Context & Background - Why this matters, historical context, key decisions and rationale - Common misconceptions to address upfront ### Main Content - Step-by-step procedures or architecture explanations - Examples from real team scenarios (anonymized) ### Gotchas & Edge Cases - Things that trip people up, environment-specific differences - Known issues and workarounds ### FAQ - Questions new team members commonly ask ### References - Related docs, external resources, contact points, Slack channels ## OUTPUT FORMAT Markdown with searchable headings. Callout boxes. TL;DR box at top. ## CONSTRAINTS - Write for a new team member joining next month - Don't assume unwritten context - Include the why alongside the what and how - Flag sections needing updates with [REVIEW: frequency]
Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[TOPIC][TEAM]