glossary-updater

To keep your project glossary up-to-date, you need to scan PRD/FRD documents and code changes for new domain terms. This skill automates that synchronization by identifying new terms from enums and types, then appending them to your glossary.md file in a structured table format.

The best way to synchronize a glossary.md file after implementing features is to analyze source documents and code base changes for new terminology. This skill reads your existing glossary, discovers new domain terms, and appends them automatically to prevent outdated terminology.

Yes, you can automatically extract domain terms from PRD and FRD documents into a central glossary. The skill scans these source documents alongside code changes to identify new terms and incorporates them into the correct sections of your project's glossary.

The glossary synchronization process requires an existing glossary file located at docs/glossary.md. The skill reads this predefined structure to understand where to append newly discovered terms from your documentation and code base changes.

To add new code enums and types to your documentation glossary, you analyze the code base for technical terminology. This skill identifies those new types during synchronization and integrates them into your glossary.md file following the existing structured table format.

You should avoid automating glossary updates if your project lacks an existing docs/glossary.md file or predefined structural sections. The skill requires a structured table format to append newly discovered terms correctly and cannot build the initial glossary architecture from scratch.