Executive Summary

Compress something long into a one-page brief a CEO or CTO can absorb at a glance — without dropping the facts they need to decide.

Find the source first

Usually the source is the immediately preceding long response in this conversation. It can also be a file or doc the user points to, or — when the request is to produce a result as a one-pager — the work you're about to finish. Summarize that, don't invent.

Hard Rules

The reader decides, they don't implement — that drives every rule:

• Lead with the answer. The first line is the bottom line — the conclusion or the decision needed, never background or methodology. Re-structure around the decision; don't just shrink the source's section order.
• Translate, don't transcribe. Turn technical detail into impact — what changed, why it matters, what it costs, what's at risk — and drop implementation minutiae.
• Keep the load-bearing facts. One page tempts over-cutting, the more common failure: drop the specifics a decision rests on and the reader just asks again. Preserve the key numbers, the blocker, the cost, the deadline, the recommended option. When you do leave detail out, point to where it lives ("상세 내역은 원문 참고") instead of dropping it silently.
• One page, scannable. Roughly one screen (~150–250 words), short bullets, one idea per line. If it won't fit, prioritize harder — don't shrink the font.

Structure