using-cuelisted

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, ignore this skill. </SUBAGENT-STOP> ## Check for work in progress first This is injected at session start, on `/clear`, and **right after a compaction**. Right after a compaction you may have forgotten the stage you were just in. Do not bridge the gap from memory — ask. ```bash <cue>/status ``` **`<cue>` is the scripts directory named in your session context, just below this skill.** Every cue-dev command is written `<cue>/<script>`; put that one path in its place and change nothing else. It is already absolute and already POSIX, so there is nothing to reassemble — a path built by hand produces `d:cuepluginscue-devscriptsstatus: command not found`, because backslashes are escapes in the shell. That has happened. It tells you which stage you reached, what comes next, and how many unrecorded rows are left in outcome.md. If it cannot find a KEY (you are not in cue-dev work), it simply fails and you move on. **Move on means move on.** Do not then list `.cue/dev/`, do not pick the newest-looking item, and do not report what is in there as work in progress. The script finds an item by the branch that item recorded; no match means nothing is in flight on this branch, and that is a complete answer. A session that treated the refusal as a prompt to go looking named four finished items as "in progress" and asked the user which to continue. **When a cue-dev script refuses, do not diagnose it yourself