recipe-agent-team-terminology-context

A terminology context standardizes vocabulary across planning, design, coding, and review by proposing canonical terms for user and code-facing language. It is needed when names differ across artifacts and tasks, requiring outputs like terminology.md and context-map.md.

Generate a context-map by collecting project terms and outputting a context-map.md file that coordinates canonical terms, aliases, decisions, and open questions across named tasks and artifact paths. This ensures durable vocabulary alignment before design begins.

You can use this terminology alignment workflow with any current project workspace that has ambiguous terms or differing names across artifacts. It operates without dependencies to collect terms from code, docs, and tests, fitting any project scale needing vocabulary coordination.

This approach distinguishes itself by producing durable artifacts like terminology.md and context-map.md to coordinate vocabulary across users, code, and tasks. Unlike basic glossaries, it actively maps aliases, decisions, and open questions to named artifact paths and agent roles.