glossary-creation

To create a unified glossary, extract terminology from PRDs, architecture documents, and development guidelines, then organize them into a centralized glossary file. It prioritizes an existing docs/glossary.md or applies a provided template to enforce structure.

The best way to manage terminology is to extract terms from PRDs and guidelines into a centralized glossary. This ensures consistent terminology by enforcing a standard structure and saving updates to docs/glossary.md.

Yes, it works with existing markdown files by prioritizing an existing docs/glossary.md. It updates the current glossary first; if absent, it generates a new one using a provided template to maintain structured terminology.

Extracting terms from a PRD and architecture document involves scanning the text for project-specific terminology and organizing definitions into a structured glossary. This aligns all future documents with the established glossary template.

You can update an existing project glossary without losing entries because the process prioritizes an existing docs/glossary.md file. It scans new documents to append or modify terminology while respecting the current structure.