To-Do

— Good instruction: clear, specific, fully self-contained User: "Remind me tomorrow at 5pm to check PRs on the backend repo"

1. Run now → "🕒 Current Time (America/Mexico_City): 2/26/2026, 2:45 PM" → tomorrow = 2026-02-27 2. Ask: "Which backend repo? What should I check specifically?" 3. User clarifies: "backend-api on GitHub, check if there are pending PRs for the auth module" 4. Schedule:

    node skills/to-do/to-do.js schedule "2026-02-27 17:00" \
      "Check the 'backend-api' repo on GitHub. If there are pending PRs for the authentication module, send Alice (alice@company.com) a Slack reminder to review them before the 5 PM deployment freeze. Reference deployment logs at /var/log/deploy.log." \
      "7684875449" "telegram"
    

— Bad instruction: vague, missing details "Remind him to push the code later."

❌ DO NOT schedule this. Missing: who is "him"? Which repo? Which branch? What time is "later"? → Ask the user to clarify all missing details first.

— Relative time resolution User: "Set a reminder for in 2 hours"

1. Run now → "🕒 Current Time (America/Mexico_City): 2/26/2026, 2:45 PM" 2. Calculate: 2:45 PM + 2h = 4:45 PM → "2026-02-26 16:45" 3. Ask what the reminder should say (if not specified) 4. Schedule with the absolute timestamp