Start with the task and its latest status
Check the affected task, the most recent update and any decision or question waiting for you. Ask the manager for a concise report if the reason is unclear. A status label alone may not explain the whole problem.
If a decision is waiting
Read the request and its related plan or file. Answer the actual decision, or ask for clarification. Confirm that the task is allowed to proceed after the response; do not approve merely to clear the queue.
If the machine is unavailable
Check that the execution computer or VPS is online and that the runner is connected. A sleeping laptop cannot continue work. Restore the connection and inspect the task’s current state before restarting or reassigning it.
If an AI or GitHub connection fails
Check the reported connection error and the relevant account, credentials or permissions using the setup guidance for your beta. Repeatedly retrying a task will not fix an expired sign-in or missing repository access.
If the output is wrong
- Describe the gap between the result and the intended outcome.
- Point to the relevant requirement, file or recorded decision.
- Ask for a scoped correction and a report of what changed.
- Review the correction and its checks before accepting the result.
What you should have at the end
A clear reason for the pause and a deliberate next step: answer, reconnect, correct or ask for help. Confirm the task’s state before triggering duplicate work.