Explain a complex document in plain language

Автор: AILesson5 мин на настройкуПроверено на:ChatGPTПроверено: 2026-08-28

Быстрый ответ

Explain difficult material for a named audience without deleting conditions or uncertainty. Укажите: Complex source, Audience and prior knowledge, Purpose and boundaries. Ожидаемый результат: A plain-language explanation, glossary, example, and accuracy notes.

1

Добавьте контекст

ваш текст остаётся в этом браузере. AILesson Prompts не отправляет его ни в модель, ни на сервер.

2

Ваш промпт

Незаполненные поля остаются видимыми как заполнители, поэтому вы всё равно можете скопировать и отредактировать промпт

Explain the source in plain language for the stated audience and purpose.

Source:
[document]

Audience and prior knowledge:
[audience]

Purpose and boundaries:
[purpose]

Use only information supported by the source. Preserve conditions, exceptions, scope, numbers, uncertainty, and distinctions that affect meaning. Define necessary terms on first use and replace avoidable jargon. Use one clearly labeled illustrative example only if it does not imply facts absent from the source. Return: one-sentence point; plain-language explanation; what changes for the reader; glossary; illustrative example; limits or ambiguities; and a factual-preservation check. Do not turn explanation into professional advice or a stronger claim.
Попробовать в Playground
Конфиденциально по умолчаниюПромпт собирается локально в вашем браузере. Не вводите конфиденциальную информацию в сервисы ИИ, если ваша организация этого не разрешает.

От исходных данных к результату

Разобранный пример

Посмотрите, как конкретный контекст превращает этот рецепт в полезный результат

Реальный ввод

Complex source
The service-level objective is 99.9% successful requests measured over a rolling 30-day window, excluding scheduled maintenance announced at least 72 hours in advance. Error-budget exhaustion triggers a release freeze, except for security fixes and changes approved by the incident commander. The objective is an internal reliability target, not a customer service-level agreement.
Audience and prior knowledge
New customer-support colleagues who know the product but not reliability engineering.
Purpose and boundaries
Help them explain incidents accurately. Do not imply contractual guarantees or tell customers what compensation they receive.

Пример вывода

One-sentence point: the team aims for 99.9% successful requests across the most recent 30 days, with specific exclusions and internal consequences, but this is not a customer contract.

Plain-language explanation: “rolling 30-day window” means the measurement period moves forward each day. Planned maintenance is left out only when announced at least 72 hours ahead. The small permitted amount of failure is called the error budget. If that allowance is used up, ordinary releases stop; security fixes and incident-commander-approved changes may still proceed.

For support: describe this as an internal target, not guaranteed uptime or a basis for compensation. Glossary: service-level objective—internal reliability target; error budget—failure allowed within that target; release freeze—temporary stop on ordinary changes. Illustrative example: an announced maintenance window 48 hours ahead would not meet the stated 72-hour exclusion. Limits: the source does not define contractual uptime, compensation, or how successful requests are calculated. All numbers, exceptions, and the SLO/SLA distinction are preserved.

Почему это работает

  1. 1

    It treats exceptions and uncertainty as meaning, not clutter to remove.

  2. 2

    Audience and purpose constraints control depth without authorizing invented advice.

Проверьте результат

  • Are every number, condition, and exception unchanged?

  • Is any illustrative example clearly separated from source facts?

  • Could the audience understand the point without unexplained jargon?

Используйте уверенно

Часто задаваемые вопросы

Практические ответы о том, когда использовать этот рецепт, что нужно предоставить и где по-прежнему важна проверка человеком

What should I prepare before using “Explain a complex document in plain language”?

For “Explain a complex document in plain language,” prepare Complex source, Audience and prior knowledge, and Purpose and boundaries. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Explain a complex document in plain language” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A plain-language explanation, glossary, example, and accuracy notes—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Explain a complex document in plain language”?

The published test record for “Explain a complex document in plain language” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Продолжайте работу

AILesson · Рекомендуемые курсы

ваш следующий шаг: примените ИИ на практике

Перейдите от понимания ИИ к выполнению задач. Практикуйтесь в составлении запросов, проверке и улучшении результатов с помощью интерактивных уроков для работы и повседневной жизни.

Просмотреть все курсы