If glossary-context.sh or glossary-finalize.sh fails (non-zero exit or "status":"error" in its JSON) print ⚠️ <error.message> and stop — except a lint error from finalize: fix the named line and retry (max 3 retries).

Steps

Audit. Run .agents/skills/pflow-glossary/scripts/glossary-context.sh → {glossary:{path,format,rows,default_path}, files_scanned, identifiers:[{name,count}]}.
Collect candidates. Read the existing glossary (if path is set) and skim README and docs for domain nouns; their language is the glossary language. In identifiers look for several names of one concept (Customer/Client/Account, Order/Purchase). Include only project-specific concepts; skip words a dictionary or the language already defines. Do not read the whole codebase.
Ask once. With one AskUserQuestion round (skip what the conversation already answers), settle: for every synonym cluster, which name is canonical; which candidates are out of scope; and, when the user asked for specific terms, anything ambiguous in them.
Draft the file per Format. New terms are added to the existing tables; existing rows are kept unless the user asked to change them.
Write. One non-interactive Bash call feeding the Markdown through a quoted heredoc:

pflow-glossary

Steps