Turn a vague request into a clear brief

작성자: AILesson4 분 소요테스트::ChatGPTClaudeGemini검토일: 2026-08-27

빠른 답변

Expose missing decisions, constraints, and success criteria before work begins. 제공할 내용: The original request, Known context. 예상 결과: A structured brief plus the questions that still need answers.

맥락 추가

텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.

The original requestKnown context

프롬프트

채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다

Turn the request below into a clear, executable brief.

Original request:
[request]

Known context:
[context]

Do not invent missing facts. Separate confirmed information from assumptions. Produce:
1. Objective
2. Target audience or user
3. Required deliverable
4. Constraints and non-goals
5. Success criteria
6. Decisions already made
7. The five highest-priority questions that must still be answered

End with a one-sentence definition of done.

Playground에서 사용해 보기

기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.

입력에서 결과까지

적용 예시

구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요

실제 입력

The original request: We need a better onboarding experience for the volunteer scheduling portal before the autumn intake.
Known context: The portal is used by new volunteers at a community food bank. The operations team can edit emails and help content but cannot change the account-creation flow this quarter. The autumn intake begins on 15 September. Support logs show that new volunteers often ask where to find their first shift, but no baseline completion data has been collected. One designer and one operations coordinator are available for two weeks.

예시 출력

1. Objective

Help newly registered food-bank volunteers find and understand their first scheduled shift before the autumn intake begins.

2. Target user

Confirmed: new volunteers using the scheduling portal. Assumption requiring validation: volunteers who contact support represent the broader onboarding audience.

3. Required deliverable

A reviewable onboarding improvement package that the operations team can implement within two weeks, covering editable emails and help content. The exact formats and number of assets are not yet confirmed.

4. Constraints and non-goals

Deadline: ready before 15 September.
Capacity: one designer and one operations coordinator for two weeks.
Changes are limited to emails and help content.
Account-creation changes and a full portal redesign are out of scope.

5. Success criteria

Reduce confusion about finding the first shift. A measurable target and baseline are still missing; the team must choose a proxy such as related support requests or successful first-shift discovery.

6. Decisions already made

Target the autumn intake, use existing editable communication surfaces, and exclude account-creation changes.

7. Highest-priority questions

Which email and help pages can be changed?
What path should volunteers follow to find a first shift?
Which support-log examples reveal the main confusion?
What metric and baseline will define improvement?
Who approves and publishes the final content?

Definition of done: The agreed email and help-content changes are approved, published before 15 September, and paired with a defined measure for first-shift discovery.

효과가 있는 이유

1
It makes the model preserve uncertainty instead of silently filling gaps.
2
The output structure turns discussion into a reviewable work artifact.

결과 확인

Are assumptions visibly separated from facts?
Could another person tell exactly when the task is done?

안심하고 사용하세요

자주 묻는 질문

이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변

What should I prepare before using “Turn a vague request into a clear brief”?

For “Turn a vague request into a clear brief,” prepare The original request and Known context. 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 “Turn a vague request into a clear brief” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A structured brief plus the questions that still need answers—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 “Turn a vague request into a clear brief”?

The published test record for “Turn a vague request into a clear brief” lists ChatGPT, Claude, and Gemini as of 2026-08-27. 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.

더 많은 탐색 방법