# Open questions

Open questions is the screen that gathers, in one place, the things to ask the stakeholder that come out of AI reviews of requirement cards, requirements and stories. Open it from 'Review and open questions' in the sidebar. When questions are scattered across phases you forget to send some, so here you can copy them all together and mark the answered ones resolved.

![PM on Rails open questions. Unresolved asks, recipients and answer status. Before: Slack threads were the source of truth. After: answers return as proposed spec updates.](https://pmonrails.com/docs-img/clarifications.png)

## When to use it

- An AI review of a requirement said "you should check this with the stakeholder".
- The premise of a story or acceptance scenario is vague, and hard to move on without an answer.
- You want to send just the unanswered questions together before a regular meeting.

## What you can do

- **Filter by unanswered / in discussion / resolved** — Show only what still needs an answer.
- **Filter by target type** — Look at questions by where they came from: requirement cards, requirements, stories and so on.
- **See only the ones waiting on you** — Narrow it down to the questions that concern you.
- **Copy the questions together** — Copy the questions on screen as a numbered list and paste them straight into an email or chat.
- **Answer from the screen** — Leave an answer as a reply, and follow the history of the exchange.
- **Resolve, or move it back to unresolved** — Mark it resolved once you have an answer, and move it back if you need to check something more.
- **Answers flow back into the spec as update proposals** — When a question is answered and resolved, the AI builds **update proposals** for the requirements, stories and scenarios in light of it (rebuilt if the answer changes). The proposals wait for approval, and the spec does not change until a person reviews the diff and applies them (only proposals an AI agent creates through the MCP tool `create_question_reflection_proposal` are written on the spot, since the call counts as the approval). **That removes the work of transcribing answers into the spec, and the risk of missing one.** Proposals from upstream text changes ([Change tracking and diff checks](https://pmonrails.com/en/docs/change-tracking.md)) are also reviewed and applied by a person.

## Differences by role

- viewer (stakeholder) can answer, but cannot mark something resolved.
- editor and above can mark it resolved once it is answered.

## Next steps

- Review and apply upstream update proposals → [Change tracking and diff checks](https://pmonrails.com/en/docs/change-tracking.md)
- Turn a gap into a requirement → [User stories and scenarios](https://pmonrails.com/en/docs/stories.md)

---

https://pmonrails.com/en/docs/clarifications