Add doc and process for tracking dev questions for users (#92)

Author: imnasnainaec

AGENTS.md

@@ -144,3 +144,7 @@ Every function and method — exported or internal — must have a JSDoc block w
 - `@throws` for every error condition the caller must handle; omit if the function never throws.
 
 Type declarations (interfaces, type aliases, enums) must have a JSDoc summary on the type itself and on each field or member whose purpose is not self-evident from its name and type.
+
+## UX decisions
+
+When key UX decisions are being made, discuss with a developer whether something should be added to `user-questions.md` for review with people outside the development team.

user-questions.md

@@ -0,0 +1,13 @@
+This document is for things about which the dev team wants feedback from users or other stakeholders.
+
+As decisions are needed in development, the developer should feel free to make the decision and add section in this document for external engagement. This _ex post facto_ review prevents unnecessary development delays.
+
+If there are two options we want users to choose from, a pr can include a switch at the top of the extension for toggling between the options in demonstration. The switch is to be removed later after a final decision is made. (We are free to do this on the `main` branch until we make our first public release.)
+
+## Topic Template
+
+Description of thing needing decisions.
+
+Explicit questions and/or clear list of options. Use multiple questions as needed: combining distinct factors into a single question leads to incomplete or confusing answers.
+
+List of relevant GitHub issues/prs/commits.