doc-architect

To identify documentation files needing updates, analyze the new feature's scope against design docs, folder READMEs, and interface docs. This process generates an impact checklist specifying exact file paths to create or update with rationales for comprehensive coverage.

The best way to plan documentation updates is running an automated impact analysis on the feature scope. It lists all design documents, API documentation, and relevant READMEs requiring modification or creation before implementation begins.

Generate a checklist by analyzing the feature's scope to determine necessary updates across design docs, folder READMEs, and interface docs. The output provides specific file paths for each documentation artifact with rationales for structured planning.

Yes, you can use this documentation impact analysis approach for any new software feature. It works by evaluating the feature scope against existing documentation structures to produce a tailored checklist of files to create or update.

Teams miss updating folder READMEs and interface docs because feature planning lacks structured impact analysis. Automating the identification of necessary documentation updates across design docs and READMEs ensures comprehensive coverage before implementation.