SMTM — /rename Reminder + Success-Criteria Gate

Two /task-* skill upgrades, both live-verified.

1. /rename session reminder

task-start.md (Step 9) and task-continue.md (Step 7, fresh-session case only) now suggest 💡 Rename this session: /rename <slug> after the first response — a live session needs a Talbot-set name to be identifiable in herdr desktop and matchable via claude --resume <name> on mobile/Remote Control; CC’s auto-default name (cwd-2char) isn’t.

“Can CC detect an already-set name?” — no. Checked session transcript .jsonl (only tool-call name fields) and ~/.claude/usage-data/session-meta/*.json (full schema, no session_name field). The name only exists transiently in the JSON the statusline script receives on stdin — not readable by the agent mid-session. Suggestion fires unconditionally; harmless to ignore if already named. Live-verified: renamed session showed correctly in the Android Claude app.

2. Success-criteria gate

task-start.md Step 5 gates on a stated definition of “done” before executing — one check, not an interview: could you tell, without asking Talbot, whether a completed attempt satisfies the ask? Uses AskUserQuestion if unclear. Deliberately lighter than task-prep.md’s existing full clarity check, and skipped when status: ready.

Proactive half (Talbot approved): added a ## Success Criteria section to both Templates/SMTM Task.md and Templates/SMTM Task — Smart.md (all 3 branches) — definition-of-done gets written at task creation instead of caught reactively. task-start.md’s gate and task-prep.md’s clarity check now read that section first, falling back to inferring from ## Tasks for pre-existing files.

Commits

• ai-config: ae838d6 (rename + gate), 0032c84 (wire gates to new template section)
• KB: 67db77e, d53bf48 (task responses), a412d03 (template section)