Avanti Software
Claude ships Ava's documentation with the code
HR & Payroll Software
Highlights
Claude reads each code change as developers commit, identifies which screens were touched, and scopes documentation capture to just those areas. As screenshots land, Claude records what's on the screen, the tab, the controls, the page state, so every article is grounded in the actual build. On merge to main, Claude reconciles the release into one coherent update, writes each article to a single documentation standard, and checks it for anything private. The update arrives as a pull request on the documentation repo, and an approver other than the author validates it before anything publishes.
The Challenge
Avanti's documentation was produced alongside feature work rather than as part of it, someone had to manually capture screens and assemble articles, so the Ava repository drifted separately from the changes that made it necessary. Because documentation sat outside the release process, it lagged: articles reflected the last manual run rather than the product's current state, coverage was uneven, and mismatched text stayed wrong until someone noticed. There was also no review step between a change and a published article, nothing required a second person before content reached customers.
The Solution
CWX built an automated workflow where Claude reads, writes, and checks documentation as part of the release pipeline itself, not after it. When a developer commits, Claude reads the change, identifies which screens it touched, and scopes capture to those areas. As screenshots land, Claude records what's on screen so every article is grounded in the actual build. On merge to main, Claude reconciles the release into one coherent update, writes each article to a single Avanti standard, and checks it for anything private before it ships as a pull request on the Ava repository.
The Implementation Process
Change: Claude reads what moved in the commit and scopes capture to those areas.
Describe: Claude reads each screen as it lands and records what's on it.
Write: Claude reconciles the release and drafts each article.
Approve: A pull request lands on the Ava repo, validated before it publishes. (An approver other than the author checks every update, nothing reaches customers without a second person.)