act

To infer context and resume a coding session after a break, the system reads recent session journals and open todos to propose the single most relevant next action for execution upon your confirmation.

The best way to determine the next action for an active workflow is to analyze active work artifacts like plans and todo lists. This mechanism identifies the next best action by reading recent context and waiting for user confirmation to execute it.

Yes, you need specific memory files to automate task resumption. This mechanism requires access to memory sources including session_journal.md, todo.md, and the plans/ directory to infer current context and propose the next action.

Yes, you can use session journals and todos for planning across multiple projects. The system applies during resumed sessions or after breaks to interpret recent work context and surface concrete actions to maintain momentum across coding sessions.

To execute a proposed action during a resumed development session, simply confirm the action surfaced by the inference mechanism. It fetches the next action based on your recent activity and executes it immediately upon your approval.

You should not use automated context inference for debugging when your memory sources are empty or outdated. The mechanism relies entirely on reading recent session journals, open todos, and active plans to accurately identify the next best action.