A check-in routine#
Open the live task list to find work that is running or needs a response. Choose one task, read its latest answer and draft only the instruction for that context. After reviewing and sending, move to the next conversation.
Use clear task names that describe the project and next objective. Rename a topic when a vague title makes selection ambiguous, but remember that naming changes metadata; it does not rewrite the task’s request.
Preserve each conversation’s context#
A prompt such as “Use option two” is understandable only in the thread that presented the options. When switching between similar projects, restate the object if needed: “Use the shorter onboarding route from your previous answer.”
CueSpec saves drafts by conversation, but you should still check where a newly transcribed instruction landed before sending. Cross-task recording and editing edge cases deserve separate verification. Current task visibility is a Codex companion capability; broad multi-agent dispatch and automatic model routing remain future work.