review-milestone-requirementslisted

# review-milestone-requirements The current "work in progress" requirements for the planned milestone live in the current milestone's `requirements.md`. The overall goal is to make that file ready enough for the work to begin — it's fine to leave some decisions to settle while doing the work if they're better solved there. This skill is the **repeatable engine** of the requirements-iteration loop — run it each time around: ``` review → (discuss) → answer → review → answer → … → converged → derive-tasks ``` Each pass does three jobs: **reconcile** the existing questions against what's now decided, **surface** the new gaps, and report whether the document has **converged**. ## review-milestone-requirements ``` /review-milestone-requirements ``` ## Milestone requirements document structure The structure of `requirements.md` is as follows: ```md # Milestone <milestone_id>: <name> ## Goal <description of the goal here> ## Relevant starting state <description of the Relevant starting state> ## Decisions <subsections with detailed requirements> ## Open questions <any open questions, each a `<open-question>` XML block> ``` The `## Goal`, `## Relevant starting state`, `## Decisions`, and `## Out of Scope` sections stay prose Markdown. The `## Open questions` section is different: it holds raw, structured `<open-question>` XML blocks (one per question, never inline next to a requirement), queried by line-oriented CLI (`awk`/`sed`/`grep` on the block boundary lines). Al