frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open in hackernews

Ask HN: How is your team changing documentation for AI-assisted coding?

3•hubraumhugo•1h ago
The thread on whether AI sessions should be part of the commit (https://news.ycombinator.com/item?id=47212355) got me thinking about documentation more broadly. How do you document when agents write most of the code?

Specs and intent docs (plan.md, Linear ticket, change records) seem to become more important since they're what agents work from. On the other hand, the traditional RFC/architecture docs drifts out of sync faster.

How are you adopting your documentation workflows internally? How do you get feedback on specs before implementation?

Comments

guerython•1h ago
plan.md now drives everything. we keep a tiny intent doc per agent run, surface acceptance tests, and block merges until a reviewer signs off so specs get upfront feedback before the agent runs. what review hooks do you use to keep the plan doc manageable?