fix: improve native OpenClaw thinking skills

office-hours: add design doc path visibility message after writing
ceo-review: add HARD GATE reminder at review section transitions
retro: add non-git context support (check memory for meeting notes)

Mirrors template improvements to hand-crafted native skills.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

openclaw/skills/gstack-openclaw-ceo-review/SKILL.md

@@ -129,6 +129,7 @@ Once selected, commit fully. Do not silently drift.
 **Anti-skip rule:** Never condense, abbreviate, or skip any review section regardless of plan type. If a section genuinely has zero findings, say "No issues found" and move on, but you must evaluate it.
 
 Ask the user about each issue ONE AT A TIME. Do NOT batch.
+**Reminder: Do NOT make any code changes. Review only.**
 
 ### Section 1: Architecture Review
 Evaluate system design, component boundaries, data flow (all four paths), state machines, coupling, scaling, security architecture, production failure scenarios, rollback posture. Draw dependency graphs.

openclaw/skills/gstack-openclaw-office-hours/SKILL.md

@@ -281,7 +281,8 @@ Count the signals for the closing message.
 
 ## Phase 5: Design Doc
 
-Write the design document and save it to memory.
+Write the design document and save it to memory. After writing, tell the user:
+**"Design doc saved. Other skills (/plan-ceo-review, /plan-eng-review) will find it automatically."**
 
 ### Startup mode design doc template:
 

openclaw/skills/gstack-openclaw-retro/SKILL.md

@@ -25,6 +25,11 @@ Parse the argument to determine the time window. Default to 7 days. All times sh
 
 ---
 
+### Non-git context (optional)
+
+Check memory for non-git context: meeting notes, calendar events, decisions, and other
+context that doesn't appear in git history. If found, incorporate into the retro narrative.
+
 ### Step 1: Gather Raw Data
 
 First, fetch origin and identify the current user: