remind

name	remind
description	Add a date-keyed reminder — surfaces on the target day

Remind

Add a reminder pinned to a specific date. Reminders show up via rubber-ducky remind list <date> and are picked up by /good-morning.

When to invoke

Trigger on any of:

• /remind <natural-language>
• "remind me "
• "on "
• " "

Examples:

• "remind me Friday to follow up with Alex"
• "on May 4th to switch checkout"
• "2026-05-11 Asana MCP SSE endpoint shuts down"
• "next Thursday to check Slack for design feedback"

If the phrasing has no parseable date ("don't let me forget", "next time I work", "add this to ASAP"), this is /asap, not /remind. Invoke the asap skill instead and stop.

"Remind me next work day" is intentionally ambiguous — route to /asap.

Arguments

$ARGUMENTS — natural-language string mixing a date and a message.

Behavior

Step 1 — Parse the date

Convert relative dates to absolute YYYY-MM-DD. Use today's date (from context) as the reference point.

• "Friday" → next Friday from today
• "May 4th" → upcoming May 4 (next year if already past this year)
• "in two weeks" → today + 14 days
• "2026-05-11" → as-is

If the date is genuinely ambiguous (e.g., "next month"), ask the user once to clarify. Don't guess.

Past dates are allowed — the user may want a retroactive note — but warn once: "That date has already passed — still add it?"

Step 2 — Parse the message

Everything that isn't the date is the reminder body. Clean it up (strip "remind me to", "on ") but keep the user's intent. Tight, TODO-style.

Step 3 — Check for a related task

If the reminder clearly references an existing wiki task (by name, ticket ref like WEB-123, or a backend identifier the workspace uses), find the task page under wiki/tasks/. If found:

• Mention the wikilink in the reminder body so it's clickable: <message> ([[<task page>]])
• If the task's due: frontmatter is unset OR later than the reminder date, offer to update it (don't do it silently):

  Want me to set [[<task page>]]'s due date to YYYY-MM-DD as well?
  

Step 4 — Dedup check

Run via Bash:

rubber-ducky remind list <date> --json

If a pending reminder on the same date has near-identical text, tell the user and let them choose. Do not write a duplicate silently.

Step 5 — Add the reminder

Run via Bash:

rubber-ducky remind add <YYYY-MM-DD> "<message>"

Step 6 — Confirm

One voice-friendly line:

Reminder set for YYYY-MM-DD: <message>

If you also updated a related task's due:, mention it on the same line:

Reminder set for YYYY-MM-DD: <message>. Also set [[<task>]] due to YYYY-MM-DD.

Step 7 — Redirect to the active task

Read active_task from today's daily page frontmatter:

rubber-ducky frontmatter get wiki/daily/YYYY-MM-DD.md active_task

If set, end with a one-liner pointing back to what was being worked on.

Rules

• Always convert relative dates to absolute dates. Never store "next Thursday" — store YYYY-MM-DD.
• Never duplicate. Same-date reminders with near-identical text are merged or updated, not appended.
• Past dates are allowed but warn once. Don't silently swallow them.
• Wiki-only operation. No external writes. No log.md entry.
• Do not write to today's daily page — reminders are a separate surface.
• Updating a related task's due: is opt-in. Ask before touching task frontmatter; the reminder itself goes through regardless.

Output

A single one-line confirmation, optionally followed by a one-line redirect to the active task. Nothing else.