Hooks, Commands, And Schedules
If ContextGo is used only as one-off conversation, it will never become a long-running work system.
These three capability types help move work from:
- one task
to:
- repeatable workflows
Hooks
Hooks are best understood as event-driven automation.
Use them when something should happen after:
- a workflow event
- a system state change
- a task boundary
Commands
Commands are reusable actions that users can invoke repeatedly without re-explaining them each time.
Schedules
Schedules are time-driven automation.
Use them when work should happen:
- every day
- every week
- on a fixed cadence
The simplest distinction
- Hooks are triggered by events
- Commands are triggered by people
- Schedules are triggered by time