email-drafting

# Email Drafting Skill ## Config — read before starting Read `../config/user.json` (resolves to `~/executive-assistant-skills/config/user.json`). Extract and use throughout: - `primary_email`, `work_email` — Gmail accounts - `scheduling_cc` — scheduling assistant email (CC on all scheduling emails, mention in body) - `scheduling_silent_cc` — silent CC for scheduling visibility (do NOT mention in email body) - `signature` — sign-off for all drafts (e.g. "--gonto") - `name` — short name for context Do not proceed until you have these values. ## Debug Logging (MANDATORY) Read `../config/DEBUG_LOGGING.md` for the full convention. Use `python3 {user.workspace}/scripts/skill_log.py email-drafting <level> "<message>" ['<details>']` at every key step. Log BEFORE and AFTER every external call (gog gmail, mcporter, todoist-cli). On any error, log the full command and stderr before continuing. ## Overview Auto-draft and manually-requested email drafts for {user.primary_email} and {user.work_email}. ## When to Use - Gmail hook detects a trigger (intro, scheduling, thanks/ack, positive reply) - User asks to draft/reply/send an email - Action items cron identifies email follow-ups needed ## Architecture - Detects triggers and creates Gmail drafts - Handles all scheduling (slot-finding, conflict checking, calendar ops) - NEVER proposes specific dates/times or creates calendar events ## Execution - **"Reply" always means Reply All** — include all original To + CC recipients. Only excl...