Address PR review comments

- Fix 'use roundup' help text to clarify multi-audience behavior instead
  of referencing a nonexistent 'default audience'
- Split bundled 'who do you report to + who is on your team' into two
  separate ask_user questions per the one-question-at-a-time rule
- Specify ~/Desktop as explicit save path with fallback prompt when
  directory doesn't exist
- Tables in README verified as correct markdown (single | delimiters)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: dvelton

skills/roundup-setup/SKILL.md

@@ -41,9 +41,11 @@ Ask these one at a time with `ask_user`:
 
 1. **"What's your role?"** -- Let them describe it however they want. Title, responsibilities, domain -- however they think about what they do. Don't force a specific format.
 
-2. **"Who do you report to, and who's on your team?"** -- Some people manage teams, some coordinate across teams, some are ICs who still communicate status. The skill works for all of them. Don't assume hierarchy.
+2. **"Who do you report to?"** -- Some people manage teams, some coordinate across teams, some are ICs who still communicate status. The skill works for all of them. Don't assume hierarchy.
 
-3. **"In one sentence, what does your team work on?"** -- This calibrates domain vocabulary. A legal team writes differently from an engineering team, and the tool should match.
+3. **"Who's on your team?"** -- Direct reports, close collaborators, whoever they work with regularly.
+
+4. **"In one sentence, what does your team work on?"** -- This calibrates domain vocabulary. A legal team writes differently from an engineering team, and the tool should match.
 
 ---
 

skills/roundup-setup/references/config-template.md

@@ -9,7 +9,7 @@
 
 Generate a briefing anytime by telling Copilot CLI:
 
-- `use roundup` -- generates a briefing for your default audience covering the past week
+- `use roundup` -- generates a briefing covering the past week; if you have one audience it uses that, and if you have multiple audiences Roundup will ask which one
 - `use roundup -- leadership briefing for this week` -- specify audience and time range
 - `use roundup -- team update since Monday` -- any natural phrasing works
 - `use roundup-setup` -- re-run setup to change your audiences, sources, or style

skills/roundup/SKILL.md

@@ -137,7 +137,7 @@ Frame it as a draft:
 
 Then offer options using `ask_user`:
 
-- "Looks good -- save to Desktop" -- Save as a file on the user's Desktop. Use a descriptive filename like `roundup-leadership-2025-03-24.md`.
+- "Looks good -- save to Desktop" -- Save as a file to `~/Desktop` by default. If `~/Desktop` does not exist or is not writable, ask the user where to save. Use a descriptive filename like `roundup-leadership-2025-03-24.md`.
 - "Make it shorter" -- Compress while keeping the key points.
 - "Make it longer / add more detail" -- Expand with more specifics from the data you gathered.
 - "Adjust the tone" -- Ask what to change and regenerate.