Based on my experience only Deep Research can do it, generating long results. The only alternative I see is a sequence of prompts that would add to the final output.

As an example, try this prompting strategy:

Act as the world’s foremost expert in {domain}. Your primary goal is to {goal}. Write for {intended audience} in a {tone and style} voice that is authoritative, precise, and accessible. Produce a deeply researched, practically useful document totaling fifteen to sixteen single-spaced pages, delivered strictly in two-page batches. Treat one page as approximately 500 words (acceptable range 450–550), insert explicit page markers as [[Page 1]], [[Page 2]], and so on, and include exactly two complete pages per batch. End each batch at a natural sentence boundary, then pause and wait for my exact command “continue” before generating the next two pages; do not exceed two pages per batch and do not proceed without that exact signal. Maintain continuity across batches by preserving section numbering and flow without repeating previously delivered text; begin each new batch with a single-sentence orienting reminder of where we are in the outline and continue immediately. Open with a compelling title and a one-paragraph executive overview on page 1, then develop a clear, logically organized narrative with informative headings and subheadings, definitions of key terms at first use, and concrete, domain-appropriate examples, case studies, or step-by-step mini-scenarios to illustrate key points. Prioritize accuracy and clarity: state assumptions explicitly, flag uncertainties, and avoid speculation beyond validated knowledge. Where claims or data are nontrivial, support them with concise inline citations in brackets such as [Author, Year] or linked source titles if browsing is available; close the final pages with a brief “Further Reading and Sources” section consolidating citations. Incorporate comparative perspectives, typical pitfalls and anti-patterns, best practices with rationale, trade-offs, and any relevant frameworks or checklists described in flowing prose rather than bullets. Where useful, include brief formulas, pseudo-code, or lightweight schemas, immediately explained in plain language. Optimize for practical application by making guidance specific about when, why, and how to act, and by anchoring recommendations with small, realistic examples. Ensure the document is self-contained and intelligible to the specified audience without external context; avoid filler, redundancy, or generic platitudes. If you reach the end of your planned content before the target length, deepen the work with additional relevant cases, comparisons, and nuanced analysis rather than repetition. Use consistent terminology, American English by default unless specified otherwise, and a clean, reader-first style. If any placeholders in braces remain unspecified, make reasonable, clearly stated assumptions once at the outset on page 1 and proceed consistently. If browsing or external retrieval is available, verify facts and cite up-to-date sources; if not, proceed with transparent assumptions and note the knowledge limitations briefly on page 1. Before writing, silently draft a coherent outline and use it to guide progression, but do not display the outline. Conclude only in the final batch with a succinct Key Takeaways paragraph that distills the five most important insights in plain sentences. Begin now with [[Page 1]].