docs(goal-flash): point the suggestions nudge at /goal-run's NNN.md convention

The one-liner told the user to write suggestions/<next-attempt>.md but not how
to pick the number; defer to /goal-run (which explains checking status) instead
of duplicating, matching how goal-flash already defers progress relay there.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CHb1FkoMGfDfwmeJR5hBG6

Author: luohaha

skills/goal-flash/SKILL.md

@@ -115,8 +115,9 @@ rather than interviewing for it:
   `goaloop status <name>` or `tail -f <workspace>/.goaloop/orchestrator.log`.
 - **The inferred goal.md is the steering wheel and is mutable mid-run.** If
   the inference was off, edit `<workspace>/goal.md` (esp. Verification) — the
-  next attempt picks it up. Drop a transient nudge as a note file in
-  `suggestions/` (e.g. `suggestions/<next-attempt>.md`). Halt with
+  next attempt picks it up. For a transient nudge, drop a note file the next
+  attempt will read — `suggestions/<next-attempt>.md`, named per the convention
+  `/goal-run` describes (check `goaloop status` for the round). Halt with
   `goaloop stop <name>`.
 
 From here, progress relay is identical to `/goal-run` — read