draft-replieslisted

If vault_path is not in context, read `~/.myna/config.yaml` first. If the file does not exist, tell the user to run `/myna:setup` and stop. # draft-replies Process the `DraftReplies` email folder. This is a dedicated workflow: the user forwards emails into `DraftReplies` with instructions about what to draft, and this skill converts them into draft files in `Drafts/`. **This skill reads ONLY the folder configured as `triage.draft_replies_folder` in `_system/config/projects.yaml`** (default: `DraftReplies`). It never reads other project email folders, the inbox, or any other folder. All drafts are for user review — never sent automatically. --- ## Before You Start Read: - `_system/config/workspace.yaml` — user identity, role, and timezone - `_system/config/projects.yaml` — get `triage.draft_replies_folder` value - `_system/config/communication-style.yaml` — tone presets, sign-offs, style preferences - `_system/config/people.yaml` — relationship tiers, aliases If the email MCP is unavailable, output: "Email MCP unavailable — cannot read DraftReplies folder." and stop. --- ## How the DraftReplies Workflow Works The user forwards an email thread into the `DraftReplies` folder. The forwarded email contains the full thread inline — potentially many replies from different people. **How to find the user's instructions:** The notes_email message is the only instruction source. Look for a message in the thread where `to` equals `email.notes_email` from workspace.yaml — that