Recipes

Recipes are starting shapes, not one-click promises. Adapt the sources, decision rule, destination, and review owner to your workspace, then test with representative input before enabling a schedule or heartbeat.

Choose a recipe by responsibility

Need	Starting shape	Recipe
A guided agent should prepare a scheduled daily view	Morning Brief agent with scheduled wakeups	Morning Brief
Someone should notice meaningful project changes	Agent with a heartbeat	Project change monitor
The same reconciliation should have independent records	Automation	Month-end close review
A fresh packet is needed before each meeting	Automation	Meeting preparation brief
Each code change needs a bounded evidence-based review	Manual automation	Pull-request review

Adapt four things

For any recipe, make the approved sources explicit, define what counts as a meaningful result, name the destination, and state which external actions require human approval. Put durable rules and reference material in the project; keep one-occurrence dates, identifiers, and requests in the run input.

Start manually. Review evidence, tool activity, approvals, usage, and the empty-result path. Add autonomy only when a named person can recognize both success and failure.