Judge Task Lifecycle
Judge how a memory changes active-task state and whether it refers to an existing task.
Install
npx skills add sno-ai/sno-station --skill judge-task-lifecycle -g -a claude-code -y- Repository
- sno-ai/sno-station1.1k
- Category
- Engineering
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 633 tokens
- Runs scripts
- No, instructions only
What it does
Judge how a memory changes active-task state and whether it refers to an existing task. Use for mem-claw task-lifecycle model calls.
Judge Task Lifecycle
Judge task meaning. Do not decide from exact wording alone.
Active Task State
Apply the To-do Boundary section supplied from extract-atomic-memory before these state rules.
Decide in this order and stop at the first step that applies.
- Does the candidate report OR INSTRUCT that an existing active task is done, finished,
handled, cancelled, or dropped? If yes, the answer is
completeorremoveon THAT task. Neveropen_or_refine, and nevernone. A report ("I finished X", "X is done") and an instruction ("mark X complete", "tick X off", "close X", "remove X from my list") both land here. An instruction to change a task's state IS the state change; do not treat it as a request you decline to act on. A candidate that speaks about an active task's ending is never a new task, however it is worded, and restating the task's name inside such a sentence is naming the task to close, not opening one. - Otherwise, if the candidate describes work still to be done, use
open_or_refine. - Otherwise use
none.
