fix(skills): workshop-start requires user review between rounds and before shutdown

- Between rounds: mandatory AskUserQuestion checkpoint before next round launches
- Wrap-up: user explicitly controls team dismissal
- Hard requirements before close: D-records filed, discussion captured, tickets created
- User reviews workshop-outcomes.md before finalization

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude/skills/workshop-start/SKILL.md

@@ -73,25 +73,35 @@ For large workshops (>6 agents), spawn participants in batches to avoid overwhel
 - SendMessage to nudge idle agents or provide clarification
 - Agents work autonomously — claim tasks, read the brief, produce responses
 
-### 7. Between Rounds
+### 7. Between Rounds — USER REVIEW CHECKPOINT (MANDATORY)
 
 When all Round N tasks are complete:
 1. Verify all agents wrote output files to `docs/workshops/{name}/`. If any are missing, nudge the agent or extract from their message and write the file yourself.
 2. Qatux reads all `*-round{N}.md` files and produces round summary in `round-{N}-notes.md`
-3. Create Round N+1 tasks (integration pass, synthesis, etc.) — include the same file output requirement
-4. Assign to agents with TaskUpdate
-5. Agents continue working
+3. **MANDATORY: Present round results to the user via AskUserQuestion before proceeding.**
+   - Summarize the key findings, votes, consensus, and tensions from the round
+   - Present open decisions that need user input (product decisions, scope calls, design direction)
+   - Ask the user whether to proceed to the next round, adjust direction, or add rounds
+   - **Do NOT create next-round tasks or synthesize proposals until the user has reviewed and approved**
+   - The user cannot see agent messages or file contents — present all key information directly
+4. After user approval, create Round N+1 tasks (integration pass, synthesis, etc.) — include the same file output requirement
+5. Assign to agents with TaskUpdate
+6. Agents continue working
 
-### 8. Wrap Up
+### 8. Wrap Up — USER CONTROLS SHUTDOWN (MANDATORY)
 
-**Always ask the user before wrapping up.** There may be more to discuss or additional rounds needed. Only proceed to wrap-up when the user confirms.
+**The user decides when the workshop ends and when the team is dismissed.** Never initiate shutdown, team cleanup, or wrap-up autonomously. Only proceed when the user explicitly says to wrap up.
 
-Wrap-up sequence:
-1. Qatux produces final `workshop-outcomes.md` from accumulated notes
-2. Qatux creates or updates diagrams (via `/d2-diagram`) for any new D-records produced by the workshop
-3. If SI is present, SI creates tickets from decided items
-4. Send shutdown_request to all agents (qatux and si last, after they finish their output tasks)
-5. TeamDelete to clean up
+Before the user dismisses the team, the following are **hard requirements**:
+
+1. **User reviews final outcomes** — Present `workshop-outcomes.md` content to the user via AskUserQuestion. Get explicit approval before proceeding to filing.
+2. **D-records filed** — All new D-records, amendments, and supersessions are written to `decisions/` domain files. This is non-negotiable — workshops that produce decisions MUST file them before shutdown.
+3. **Discussion captured** — Qatux produces final `workshop-outcomes.md` from accumulated notes. Qatux creates or updates diagrams (via `/d2-diagram`) for any new D-records produced by the workshop.
+4. **Tickets created** — If SI is present, SI creates tickets from decided items and the user reviews the ticket list.
+5. **User gives explicit go-ahead to dismiss** — Only after steps 1-4 are complete AND the user confirms, send shutdown_request to all agents (qatux and si last).
+6. TeamDelete to clean up.
+
+**Never shortcut this sequence.** Filing D-records and capturing the discussion are not optional cleanup — they are workshop deliverables.
 
 ## Workshop Format: Interview Mode