Hey HN,<p>Every time software is released, documentation goes out-of-date.<p>I was a PM for 3 years and by far the worst part was the bookkeeping required to draft updates to documentation, marketing materials, sales decks and demo videos every time a new feature was shipped. It was a huge time sink for myself and our engineers. Product teams want to focus on making the best products possible, and maintaining these materials is therefore an afterthought.<p>Unfortunately, they are critical for a business to operate. Bad docs lead to increase in support workload and higher churn.<p>Today this problem is solved by hiring dedicated roles to maintain these assets (tech writers, sales enablement), which is expensive and adds processes. With LLMs, we think the same can now be achieved for less.<p>That’s why we’re building AutoDocs, a tool that automatically finds which parts of your documentation need updating, every time a product is changed. We ingest JIRA / Linear releases, search for internal context to understand the change, and then flag the documentation that needs updating.<p>We’ll next start automatically drafting updates to docs, and then move into other content such as help centres, sales decks and product videos. Our mission is to make it 10x easier to have a full set of assets that stays in sync with the codebase.<p>We’d love to hear your honest feedback!
What kind of internal context are you retrieving? I'd imagine you would need access to the codebase to have a thorough enough understanding of the docs, because if not, I feel like most Linear issues + internal documents are not descriptive enough.