plan-document-review

API validation in planning documents verifies API signature accuracy and confirms that documented changes match the actual API specifications. This ensures consistency and prevents implementation errors by enforcing strict accuracy across your project plans.

You can review planning documents stored as markdown files, such as those located in a docs directory. The tool validates the content consistency and completeness of these documentation files to ensure they are ready for implementation workflows.

Documentation synchronization is a core part of the plan review process, ensuring that API updates and protocol details are accurately reflected. The review verifies consistency between listed impact files and the documented changes to maintain accuracy.

The primary limitation is that it strictly enforces completeness and consistency, meaning any missing sections, inaccurate API signatures, or absent impact files will cause the review to recommend improvements before the document meets engineering standards.