mlsanityData to 14 Oct 2026

DoGBench: Can Agents Meet Expert Standards for User-Facing Documentation?

arXiv 2609.39909 ↗First posted 30 Sep 2026cs.SE cs.AIcited by 0

Not on the map. Why?

Abstract (arXiv)

We introduce DoGBENCH (Documentation Generation Benchmark), to our knowledge, the first benchmark for generating and maintaining real user-facing software documentation. It asks whether an agent can produce documentation that experienced technical writers would accept in review. The benchmark contains 292 items from open source projects, including Helm, PostHog, and Mautic. Each item gives the agent a pre-change repository and a trigger, such as a code pull request or a reported documentation gap. The agent must first decide whether the documentation needs an update. For items that need one, the agent must produce an acceptable patch in one attempt. For items that do not need updates, the agent must abstain. Task-specific rubrics, validated with project maintainers, score each patch on accuracy, completeness, reader guidance, placement, and repository conventions. The composite score combines patch quality with correct abstention, and a score of 100 means an agent meets every requirement for the task. Scores should not be interpreted as a percentage of an expert's capability. We evaluated seven agents. The highest-scoring agent reached 47.3 out of 100 on the 117-item held-out split. In a separate audit of 1,267 patches, the most common failure modes were task-completion gaps (45.5%), technical inaccuracies (36.6%), and incomplete conceptual or reference coverage (32.5%). Analysis of the corresponding trajectories identified three key patterns associated with these failures: (1) describing interfaces without examining how readers use them (36.0%), (2) missing decisive evidence and filling the gaps with plausible assumptions (33.1%), and (3) stopping after finding the first plausible documentation surface and leaving other affected pages stale (30.1%).

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 22 of its 23 references that are in the map. First posted on arXiv 30 Sep 2026.

Builds on

22 of 23 references.

References · 22

  1. 2023Let's Verify Step by Stepcited by 3,789
  2. 2023SWE-bench: Can Language Models Resolve Real-World GitHub Issues?cited by 3,373
  3. 2022Scaling Laws for Reward Model Overoptimizationcited by 1,095
  4. 2021CodeXGLUE: A Machine Learning Benchmark Dataset for Code Understanding and Generationcited by 744
  5. 2024LLM Evaluators Recognize and Favor Their Own Generationscited by 686
  6. 2019CodeSearchNet Challenge: Evaluating the State of Semantic Code Searchcited by 654
  7. 2025RAGEN: Understanding Self-Evolution in LLM Agents via Multi-Turn Reinforcement Learningcited by 386
  8. 2023NLP Evaluation in trouble: On the Need to Measure LLM Data Contamination for each Benchmarkcited by 348
  9. 2024Who Validates the Validators? Aligning LLM-Assisted Evaluation of LLM Outputs with Human Preferencescited by 144
  10. 2025Process Reward Models for LLM Agents: Practical Framework and Directionscited by 85
  11. 2024Belief Revision: The Adaptability of Large Language Models Reasoningcited by 30
  12. 2026RubricBench: Aligning Model-Generated Rubrics with Human Standardscited by 28
10 more
  1. 2024Mitigating the Bias of Large Language Model Evaluationcited by 17
  2. 2025Do not Abstain! Identify and Solve the Uncertaintycited by 11
  3. 2026Failing to Falsify: Evaluating and Mitigating Confirmation Bias in Language Modelscited by 9
  4. 2025Do LLM Agents Know How to Ground, Recover, and Assess? A Benchmark for Epistemic Competence in Information-Seeking Agentscited by 7
  5. 2025CaRT: Teaching LLM Agents to Know When They Know Enoughcited by 7
  6. 2026Look Before You Leap: Autonomous Exploration for LLM Agentscited by 6
  7. 2025CoDocBench: A Dataset for Code-Documentation Alignment in Software Maintenancecited by 5
  8. 2026Correct Answers from Sound Reasoning: Verifiable Process Supervision for Language Modelscited by 4
  9. 2026Evaluating Repository-level Software Documentation via Question Answering and Feature-Driven Developmentcited by 2
  10. 2026Deep Research as Rubric for Reinforcement Learningcited by 2

Built on by

Not cited yet.