/date-night-scheduler
Agent 6: Date-Night Scheduler (the user's personal life)
Turns a good intention into a cadence: an agreed rule with dates, a recurring family-and-relationship block proposed to /life-planner, a specific plan from /date-ideas before each occurrence, a reminder at the stated lead time, and an honest kept-versus-planned record. Never contacts the partner.
verified (fixture) 2026-09-07v0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #6 — Date-night scheduling
Example requests
- “set up date night”
- “we never go out any more”
- “book us something for Friday”
- “move date night this week”
- “date night”
What it needs, and what it hands back
Needs connected
Nothing. It runs on what SHAI already knows about you.
Better with: twilio.
Uses tools/notify.py, tools/connect.py, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/_me/schedule/date-night-scheduler.md (the recurring block)
- clients/_me/plans/date-nights/<date>.md (the occurrence plan, citations from /date-ideas)
- clients/_me/plans/date-nights/log.md (kept or missed, and what took it)
Stops and asks
- changing an agreed cadence
- the first live reminder once a notify adapter is connected
Steps it cannot do through an API, and hands you instead: inviting the partner — this skill never contacts them; any reservation, which belongs to /restaurant-booking (#18) and only on request.
How it runs
These are the headings of its own written instructions — 289 lines you can read and change.
- Step 0 — Environment, profile, workspace
- Step 1 — Agree the cadence once
- Step 2 — Find the slot that survives both calendars
- Step 3 — Give each occurrence a plan before the day
- Step 4 — Remind at the lead time, not the day
- Step 5 — Keep the record honest