recaplisted

Produce a **functional-improvement summary** of a PR or issue: what the work *did* (a merged/open PR) or *hopes to do* (an open issue), written for a technical collaborator who wants the feature perspective — **not** the implementation walkthrough. `/recap` is the single-target companion to `/standup`. `/standup` rolls up *all* recent activity across a time window for a daily report; `/recap` zooms in on **one** PR or issue and renders its functional story as nested bullets (or a table). Reach for `/standup` for "what happened lately"; reach for `/recap` for "explain this one PR/issue to my collaborator." ## Output modes | Mode | Flag | Effect | |------|------|--------| | Nested bullets | *(default)* | Top-level bullet = functional change; sub-bullets = scope/notes | | Table | `--table` | Markdown table with `Change \| Notes` columns | | Full | `--full` | Relax the word budget; keep nested-bullet (or table) structure | | Technical | `--technical` | Add a second tier of detail per bullet (mechanism, files, key endpoints) **without** removing the conversational top-level bullet | Flags compose: `--table --technical` adds a third "Technical detail" column; `--full --technical` keeps both expansions. ## Step 1: Parse arguments and flags Parse `$ARGUMENTS`. **Extract flags first**, then interpret whatever remains as the target identifier. - **Flags** (any order, anywhere in `$ARGUMENTS`): `--table`, `--full`, `--technical`. Set a boolean for each; strip them from the argume