# Context Rot in AI-Assisted Software Development: Repurposing Documentation Consistency for AI Configuration Artifacts

arXiv: https://arxiv.org/abs/2606.09090 · HTML: https://mlsanity.com/paper/2606.09090/

## Key facts

- Cited by 2 papers in the map (data through 14 Oct 2026).
- Builds on 6 of its 17 references that are in the map.
- First posted on arXiv 8 Jun 2026.

## Builds on (most cited first, 6 of 6)

- [On the Impact of AGENTS.md Files on the Efficiency of AI Coding Agents](https://mlsanity.com/paper/2601.20404/) (2026)
- [Context Engineering for AI Agents in Open-Source Software](https://mlsanity.com/paper/2510.21413/) (2025)
- [Harness Engineering for Agentic AI Coding Tools: An Exploratory Study](https://mlsanity.com/paper/2602.14690/) (2026)
- [Detecting Outdated Code Element References in Software Repository Documentation](https://mlsanity.com/paper/2212.01479/) (2022)
- [Wait, wasn't that code here before? Detecting Outdated Software Documentation](https://mlsanity.com/paper/2307.04291/) (2023)
- [A Dataset of Agentic AI Coding Tool Configurations](https://mlsanity.com/paper/2605.08435/) (2026)

## Built on by (most cited first, 2 of 2)

- [When and How Context Rot Appears in Coding Agents: A White-Box Study of Agent Skills in Code Auditing](https://mlsanity.com/paper/2607.17937/) (2026)
- [From Agent Behaviour to Agent-Friendly Documentation: An Empirical Study of How Coding Agents Discover, Read, and Write Technical Documentation](https://mlsanity.com/paper/2608.20195/) (2026)

## Abstract (arXiv)

Developers increasingly provide AI coding assistants with persistent context through configuration files such as CLAUDE.md, AGENTS.md, and .cursorrules. These files describe code elements, architecture, and development conventions, forming the context that guides AI tool behavior across sessions. As software evolves, this context can become stale, a phenomenon we call context rot. While AI configuration artifacts are new, the underlying consistency problem connects to decades of software documentation research. Researchers have built tools to check consistency between documentation and code, spanning README files, code comments, API documentation, architecture descriptions, and installation instructions. We argue that this existing toolbox is an immediate starting point for detecting context rot, and we present a research roadmap mapping documentation consistency approaches to corresponding problems in this new setting. As preliminary evidence, applying an existing README/wiki consistency checker to a statistically representative sample of 356 repositories identifies stale code element references in 23.0% of repositories, showing that traditional documentation consistency tools can already surface context rot.