Create an article outline for a goal and audience

작성자: AILesson5 분 소요테스트::ChatGPT검토일: 2026-08-28

빠른 답변

Design a claim-and-evidence structure that moves a specific reader toward a defined outcome. 제공할 내용: Article goal, Audience and context, Material and constraints. 예상 결과: A sequenced outline with section jobs, evidence needs, transitions, and scope controls.

맥락 추가

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

Article goalAudience and contextMaterial and constraints

프롬프트

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

Create an article outline for the stated goal and audience.

Desired change in understanding, decision, or action:
[goal]

Readers, prior knowledge, questions, stakes, objections, and reading context:
[audience]

Verified material, required points, exclusions, length, format, tone, and deadline:
[material]

Use only supplied facts as claims. Start with the reader's need and design a logical progression toward the article goal. Return: one-sentence promise; scope and non-goals; working thesis; 2–3 structural options with trade-offs; recommended outline with each section's reader question, purpose, key claim, supporting evidence, example or visual need, transition, and approximate share of length; objection and uncertainty placement; introduction and conclusion jobs; evidence gaps; and a drafting order. Avoid generic headings, repetitive sections, clickbait, and claims whose evidence is absent.

Playground에서 사용해 보기

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

입력에서 결과까지

적용 예시

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

실제 입력

Article goal: Help managers of 20–100-person organizations decide whether to introduce a written meeting-decision log and start a two-week trial.
Audience and context: Busy non-specialist managers. They know meetings lose decisions but worry another template creates administration. They will scan a 1,200-word article on a professional blog. They need a low-risk next step, not software advice.
Material and constraints: Verified internal sample: in 36 project meetings, 11 later disputes involved unclear decisions or owners. After one team trialed a log for six weeks, 19 of 21 decisions had owner/date fields; no causal productivity result was measured. Required: define a decision log, show minimum fields, address overhead, explain when not to log, give a two-week trial. Exclude claims that logs improve productivity. Calm practical tone.

예시 출력

Promise: show managers a minimal, reversible way to make consequential meeting decisions traceable without turning every conversation into paperwork. Thesis: a decision log is useful when it records only consequential decisions, evidence, ownership, and change—not as a full meeting archive.

Alternative structures: problem→tool→trial is fastest for scanning; story-led is engaging but risks overgeneralizing one team; field-by-field guide is practical but may delay the decision. Recommend problem→tool→trial.

“What keeps getting lost?” 15%: define the 11/36 dispute observation and its limits; transition from memory failure to a narrow artifact. 2. “What is a decision log?” 20%: minimum fields—decision, date, decision-maker, rationale/source, owner/due date if action, status; visual: one anonymized row. 3. “Will this create more admin?” 20%: distinguish decisions from discussion; state what not to log; use 19/21 completeness only as trial evidence, not productivity proof. 4. “When should we skip it?” 10%: routine reversible choices and sensitive content governed elsewhere. 5. “How do we test it safely?” 25%: two-week scope, owner, review questions, stop/adjust rules. Conclusion 10%: invitation to run the reversible trial.

Evidence gaps: time spent maintaining the log and dispute trend after adoption. Draft sections 2 and 5 first, then evidence, objection, intro, and conclusion.

효과가 있는 이유

1
Reader questions give each section a necessary communication job instead of merely naming a topic.
2
Evidence fields expose unsupported sections before prose makes them sound finished.

결과 확인

Does every section answer a distinct reader question and advance the article goal?
Are claims, evidence, objections, and uncertainty placed explicitly?
Do estimated section shares fit the stated length and avoid repetition?

안심하고 사용하세요

자주 묻는 질문

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

What should I prepare before using “Create an article outline for a goal and audience”?

For “Create an article outline for a goal and audience,” prepare Article goal, Audience and context, and Material and constraints. 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 “Create an article outline for a goal and audience” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A sequenced outline with section jobs, evidence needs, transitions, and scope controls—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 “Create an article outline for a goal and audience”?

The published test record for “Create an article outline for a goal and audience” 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.

더 많은 탐색 방법