Continue work between sessions
Useful continuity means the next session can recover the goal, accepted decisions, completed work and next verification. Your agent should be able to continue from the last verified result without repeating setup or reopening unchanged approvals.
Egbe keeps project work under egbe-docs/ in your product repository. Requirements and design, editable playbooks, research, development plans, campaigns and results can live alongside the relevant evidence. Create the records the work needs and use links to make them easy to find.
Leave a concrete checkpoint
Section titled “Leave a concrete checkpoint”Before a handoff, ask your agent to preserve the current result, remaining dependency, next action and how it will be verified. Include the source and limits of significant decisions. Keep credentials in the appropriate private store and exclude working records from public builds.
Save a continuation note for this product change. Include the accepted behavior, last verified result, remaining checks and exact next action. Link the relevant plan and evidence. When we resume, recover this context and continue within the existing approval.
Expect a usable handoff, with clear ownership for anything another person must do. “Waiting for access” should identify which access is needed, who can provide it and what work follows. An uncertain operation should be reconciled before it is repeated.
Decide whether recurring work helps
Section titled “Decide whether recurring work helps”Use a recurring check when something can change and there is a useful response to that change. Examples include evaluating an active experiment, watching a material product failure or continuing an agreed Business Loop. A one-time uncertainty may be better handled by a focused task.
Agree the responsibility, cadence, sources, action scope, destination and notification condition. Timing should follow expected signals, reporting delays and risk. You can request a regular digest; otherwise, meaningful changes are a useful basis for updates.
Help me set up a weekly Business Loop in this project. Show the proposed schedule, sources, allowed actions and where updates will arrive. Keep its initial scope to reviewing progress and recommending the next step. Ask me to agree the schedule before enabling it.
Verify the arrangement
Section titled “Verify the arrangement”Scheduling uses the mechanism available in your agent’s environment. The runner must have access to the project’s current methods and records. A local runtime must remain awake and available at the scheduled time; a saved task cannot keep a sleeping or closed environment executing.
Your agent should verify registration and, where feasible, perform a read-only check of access and delivery. The handoff should identify what is configured, what remains unverified and how to pause or change it. Preserve existing schedules and avoid overlapping reviews.
When scheduling is unavailable, request the same Business Loop manually. Keep the checkpoint intact so work remains ready to continue. Use Troubleshooting for connection or environment problems.