Dataset Documentation Writer
Document dataset fields, provenance, collection methods, formats, caveats, access rules, and intended use so analysts can evaluate and reuse the data safely.
Prompt
Produce **dataset documentation writer** for the stated situation. Read “dataset documentation writer prompt” as a request for an actionable artifact, then choose the depth and format that best serves that artifact. ## Before the work begins — Dataset Documentation Writer - [OUTPUT_AUDIENCE] — for Dataset Documentation Writer, supply the relevant output audience. If unavailable, label [OUTPUT_AUDIENCE] `unknown`; never infer it. - [SCOPE] — for Dataset Documentation Writer, supply the relevant scope. If unavailable, label [SCOPE] `unknown`; never infer it. - [METHOD] — for Dataset Documentation Writer, supply the relevant method. If unavailable, label [METHOD] `unknown`; never infer it. - [DEFINITIONS] — for Dataset Documentation Writer, supply the relevant definitions. If unavailable, label [DEFINITIONS] `unknown`; never infer it. - [RESEARCH_QUESTION] — for Dataset Documentation Writer, supply the relevant research question. If unavailable, label [RESEARCH_QUESTION] `unknown`; never infer it. - [DATA] — for Dataset Documentation Writer, supply the relevant data. If unavailable, label [DATA] `unknown`; never infer it. - [REQUIRED_POINTS] — for Dataset Documentation Writer, supply the relevant required points. If unavailable, label [REQUIRED_POINTS] `unknown`; never infer it. - [SOURCE_QUALITY_RULES] — for Dataset Documentation Writer, supply the relevant source quality rules. If unavailable, label [SOURCE_QUALITY_RULES] `unknown`; never infer it. ## Build process — Dataset Documentation Writer 1. Draft only after locking the audience, purpose, facts, voice, and desired action. 2. Deliver a publishable version plus a compact rationale for important choices. 3. Evaluate provenance, recency, relevance, and limitations before synthesizing conclusions. 4. Use traceable evidence references and label uncertainty explicitly. 5. Report uncertainty and methodological limitations. 6. Make every conclusion traceable to supplied material. 7. Define inclusion boundaries before evaluating evidence. 8. Assess source quality and relevance independently. 9. Boundary for Dataset Documentation Writer: Do not create citations, findings, sample sizes, quotations, or certainty beyond the supplied sources and data. ## Required result — Dataset Documentation Writer - **Scope statement for Dataset Documentation Writer** — Dataset Documentation Writer weak points, unknowns, and dataset documentation writer prompt limits. - **Evidence map for Dataset Documentation Writer** — dataset documentation writer prompt → verify Dataset Documentation Writer before use. - **Synthesis for Dataset Documentation Writer** — dataset documentation writer prompt evidence → Dataset Documentation Writer; omit preamble. - **Confidence and limitation for Dataset Documentation Writer** — material inputs for Dataset Documentation Writer, each connected to dataset documentation writer prompt. - **Next research question for Dataset Documentation Writer** — ready-to-use Dataset Documentation Writer, formatted for dataset documentation writer prompt. ## Human review points — Dataset Documentation Writer Finish with a compact integrity check for Dataset Documentation Writer: factual support, task fit, internal consistency, usability, and required human review.
How to use this prompt
Replace only the bracketed fields relevant to your situation. Keep unknown information marked as unknown, paste the completed prompt into a capable AI assistant, and review the result before using it.
Best AI model
ChatGPT • Gemini • capable reasoning assistants
