메뉴
Schedule a follow-up pulse for later checking. Use when user says 'remind me', 'check back', 'follow up', something needs verification later, or waiting for a response/action. Handles both aperiodic pulses (non-hour times) and Diary entries (hour-aligned times).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | schedule-followup |
| description | Schedule a follow-up pulse for later checking. Use when user says 'remind me', 'check back', 'follow up', something needs verification later, or waiting for a response/action. Handles both aperiodic pulses (non-hour times) and Diary entries (hour-aligned times). |
| disable-model-invocation | false |
Schedule future wake-ups for checking on tasks, responses, or events.
Invoke this skill when:
Extract from $ARGUMENTS or context:
Examples:
Use Aperiodic Pulse when:
Use Diary Entry when:
Why this matters: Aperiodic pulses at hour-aligned times will collide with automatic periodic pulses, causing duplicate wake-ups.
Map urgency to priority levels:
Critical (🚨):
High (🔔):
Normal (⏰):
Low (📋):
Use schedule_pulse() MCP tool:
schedule_pulse(
scheduled_at="[parsed time]",
prompt="[what to check/do]",
priority="[critical/high/normal/low]",
sticky_notes=["[context line 1]", "[context line 2]"]
)
Prompt format: Be specific about what to do when pulse fires:
Sticky notes: Include context you'll need later:
Example:
schedule_pulse(
scheduled_at="in 1 hour",
prompt="Check if Sarah replied to ski trip proposal in group chat",
priority="normal",
sticky_notes=[
"User asked group about weekend trip to Mammoth",
"Waiting for Alex and Jamie to confirm",
"Need to book by Friday if going"
]
)
Append to Diary/YYYY-MM-DD.md:
## Scheduled for [TIME]
- **Task**: [what to do]
- **Context**: [why/details]
- **Priority**: [level]
Example:
## Scheduled for 08:00 AM
- **Task**: Remind user about team standup at 9 AM
- **Context**: Weekly standup, user sometimes forgets
- **Priority**: Normal
## Scheduled for 14:00 PM
- **Task**: Check if PR #123 was reviewed
- **Context**: Blocking deployment, need review by EOD
- **Priority**: High
Send confirmation via send_notification() or direct response:
Examples:
✓ Set follow-up: Check Sarah's response in 1 hour
I'll ping you at 3:15 PM if no reply yet.
✓ Reminder added to Diary for tomorrow 8 AM:
"Call John re: project proposal"
The periodic pulse will remind you then.
✓ Scheduled 3 follow-ups:
• In 30 min: Check PR review status
• At 2 PM: Remind about client call
• Tomorrow 9 AM: Review weekend plans
I've got you covered!
Append to Diary/YYYY-MM-DD.md:
[HH:MM] Scheduled follow-up
- What: [description]
- When: [time]
- Type: [aperiodic pulse / diary entry]
- Priority: [level]
- Reason: [user request or proactive]
Relative times:
Absolute times:
Ambiguous times:
Recurring:
User says "remind me later" (vague):
Time conflict with existing pulse:
list_upcoming_pulses()Past time ("remind me at 2 PM" but it's already 3 PM):
Recurring follow-ups:
User cancels or changes mind:
cancel_pulse(pulse_id) for aperiodic| Time Type | Hour-Aligned? | Method | Example |
|---|---|---|---|
| 2:30 PM today | No | Aperiodic pulse | schedule_pulse("today at 2:30 PM", ...) |
| 8:00 AM tomorrow | Yes | Diary entry | Append to tomorrow's Diary |
| In 45 minutes | Maybe | Check result time, choose method | If lands on hour → Diary, else → Pulse |
| Next Monday 9 AM | Yes | Diary entry | Append to Monday's Diary |
| In 2 hours | Maybe | Calculate, then choose | If result is hour-aligned → Diary |
The goal is for the user to: ✅ Trust you'll remember (mental load reduced) ✅ Know exactly when you'll follow up ✅ Be reminded at the right time ✅ Have full context when reminder fires
Push generic improvements from your private desk back to the public template remote using git worktrees for safe, isolated editing. Use when you have improvements (skills, CLAUDE.md refinements, documentation) that would benefit all users.
Nightly consolidation and organization of the Desk. Analyzes the day's Diary entries, condenses verbose logs, extracts patterns, integrates session metrics, and surfaces user feedback. Runs overnight when user is sleeping - be thorough. Auto-invoke on overnight pulses (10 PM - 6 AM) or when Diary needs cleanup.
Scientifically validate Desk changes that affect Reeve's behavior. Use BEFORE committing non-trivial changes to CLAUDE.md, skills, Goals/, or Responsibilities/. Runs isolated test pulses with positive/negative cases to verify the change produces desired behavior under realistic conditions.
Daily morning briefing at 8:00 AM (or when user wakes up). Provides calendar summary, priorities from Responsibilities, urgent items, and suggested focus areas. Auto-invoke when it's 8 AM periodic pulse, user says 'morning briefing', or user just woke up.
Analyze Claude Code sessions for metrics and retrospection. Parses JSONL session files to extract message counts, tool usage, token consumption, and user feedback patterns. Used by daily-retrospection for budget tracking.
Reeve's runtime architecture (daemon, Hapi, MCP servers, pulse lifecycle). Invoke when debugging, explaining how Reeve works, or understanding the stack.