Explain a Technical Concept

Context

Technical concepts — data lineage, MDM golden records, dbt models, schema-on-read — are often explained in ways that assume the reader’s background. This prompt requests an explanation tuned to a specific audience’s level and communication style, using plain language and a concrete analogy. It is useful whenever you need to bridge between engineering and non-technical stakeholders, onboard a new team member, or prepare talking points for a presentation.

Works with both Gemini (for quick one-off explanations) and build-cli (when the concept is tied to a specific codebase or system that the AI has context on).

The Prompt

Explain [CONCEPT] to [AUDIENCE].

The explanation should:
- Use plain language — avoid jargon unless you define it
- Include a concrete, real-world analogy or example
- Be no longer than [SHORT (3-4 sentences) / MEDIUM (1 paragraph) / DETAILED (step-by-step)]

[CONCEPT]: [e.g. "data lineage", "MDM golden record", "what a dbt model is"]
[AUDIENCE]: [e.g. "a business analyst with no engineering background", "a senior engineer new to data governance", "a department head"]

Usage Instructions

Choose your tool:
- Gemini: works well directly in a Google Doc or Chat for quick one-off explanations.
- build-cli: use when the concept is tied to a specific codebase, schema, or system the AI has context on.
Copy the prompt above.
Fill in [CONCEPT] with the specific technical concept you want explained.
Fill in [AUDIENCE] with a description of who will read the explanation — the more specific the better (their role, their background, their likely follow-up questions).
Choose the length: SHORT for a quick clarification, MEDIUM for a summary, DETAILED for a full walkthrough.

Example Output

For [CONCEPT]: "MDM golden record" to [AUDIENCE]: "a business analyst with no engineering background" at MEDIUM length:

A golden record is the single, authoritative version of a customer (or product, or location) that exists in your Master Data Management system. Think of it like a customer profile that has been carefully assembled from multiple sources — your CRM, your billing system, your web platform — where the MDM system has picked the best (or most recent, or most trusted) value for each field from each source. Instead of three slightly different records for the same person across three systems, you get one “golden” version that everyone in the business can rely on. When a new record arrives, the MDM system decides whether it’s a new person or a match to an existing golden record.

Follow up with: “Now give me an analogy I could use in a 5-minute presentation to senior stakeholders.”