goal-pulse

Goal Pulse

Advance the current Goal at the fastest effective pace. Spend work on the deliverable: no stalling, busywork, or substituting plans and reports for execution. A pulse is a cue to act, not a request for another status report.

Act on the bottleneck

• When a worker delivers a complete artifact, read it promptly, verify the remaining obligation, and perform the next authorized acceptance or handoff step. Do not leave it waiting for a batch.
• Delegate substantial bounded work through the user's authorized workers. Give each worker the complete target, real inputs, owned files and acceptance method. Preserve the agreed division of labor.
• If the same blocker survives two worker rounds without meaningful progress, take over the specific gap or change the decomposition. Preserve the source, failed evidence and session; transfer ownership before editing. A healthy long computation or a new verified result is progress.
• Keep independent work moving while a blocked line has a saved breakpoint. Reuse working code, caches and valid checks. Repair the missing connection without restarting the whole task.
• Choose the next action that changes the deliverable. Cut repetitive polling, cosmetic rewrites, speculative corner cases and repeated reviews of unchanged work. Run checks that resolve an actual uncertainty or meet a stated requirement.
• Count complete accepted deliverables. Keep the original target, difficulty, acceptance criteria, authorization and budget. Queued jobs and partial modules remain work in progress.

Use the project's existing state files for essential breakpoints. Give normal progress updates and answer the user; do not write an extra acknowledgement or report just because a pulse arrived.

Choose the host route first

Claude Code: read the native cron instructions. Use CronList, CronCreate, and CronDelete in the current conversation, or the documented /loop 30m equivalent. Start or resume of /goal, or an explicitly authorized long autonomous task, enables reminders by default after installation. Dispatch start, status, stop, or pulse before acting: a scheduled pulse executes one reminder and never creates another cron. Honor a user's opt-out until they ask to enable reminders again. Only the main agent manages the reminder. Continue in that reference; the Python commands below belong to Codex.