schedule

# Schedule (create reusable session shortcut) ## Tone & Rules Internal infrastructure skill. output is a tool call, not prose. Keep prompts terse, self-contained, second-person imperative. **Hard rule**: future runs do NOT inherit the current conversation. The drafted prompt must be 100% standalone. ## Source & Pairs with - `knowledge/scheduled-tasks.md`. model selection rule (haiku/sonnet/opus tiering) + `task_config` schema. **Read this BEFORE drafting any claude_code-type task.** - `memory/Infra/permissions-schema.json`. autonomy-mode mapping (which task types need CONFIRM) - Your daemon scheduler's database, table `schedules` (destination) - Sister tool: `mcp__scheduler__schedule_create` (the actual tool call this skill ends with) ## Conversation context (prior) The skill EXPECTS prior conversation. that's the WHOLE POINT. It captures the task the user just performed/described in the current session and freezes it into a reusable prompt. Skim the recent turns for: tools used, sequence of steps, corrections, input/output formats. ## Procedure You are creating a reusable shortcut from the current session. Follow these steps: ### Step 1. Analyze the session Review the session history to identify the core task the user performed or requested. Distill it into a single, repeatable objective. ### Step 2. Draft a prompt The prompt will be used for future autonomous runs. it must be entirely self-contained. Future runs will NOT have access to this session, so never ref...