aops-core/skills/continue/SKILL.md
Pause and hand back to the user with work still IN PROGRESS — emit a scannable resume summary and checkpoint the bound task, WITHOUT concluding. Use /end-session or /dump to finish the task completely.
npx skillsauth add nicsuzor/academicops continueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The lightweight exit path. Use it when your work is not done — you need the user's input, or you are waiting — and you want to hand control back cleanly WITHOUT concluding the task.
This is the THIRD exit option, in addition to the two that finish the task completely:
/end-session — canonical close (commit, push, PR, release the task, reflection)./dump — emergency bail (fast resume task + short handover, no commit/PR)./continue (this skill) — pause only: the bound task stays in_progress,
nothing is committed, pushed, released, or reviewed. It just leaves a clean,
scannable pickup point in BOTH the chat and the task, then hands back.Running /continue opens the Stop gate, so you hand back without the honesty /
handover block firing — because this skill already delivers the honest,
scannable summary those gates exist to require.
Write a single block designed to orient a user who returns with no memory of the session. It MUST be EASILY SCANNABLE (short bullets, plain words, every id / branch / task named in 3–8 words). Use exactly these parts:
### Resume <UTC-timestamp>
- **You asked**: <the user's ORIGINAL ask, one sentence>
- **So far**: <2–4 bullets: the conversation / what was decided>
- **I did**: <what you actually did this session — concrete, with evidence refs>
- **Next**: <the single recommended next step, phrased so the user can act or approve>
- **Waiting on / watch out**: <what you're blocked on; any in-flight side effects (uncommitted files, running processes)>
Call mcp__pkb__update_task on the bound task:
session_id to $AOPS_SESSION_ID.status — the work is ongoing; the task stays in_progress.### Resume <UTC-timestamp> block (verbatim) to the task body.The chat summary IS the task checkpoint — write the one block to both. If no task is bound, skip the task write and say so in the chat block.
Print the resume block to the user, then stop. Do not commit, push, open a
PR, or release the task — /continue is a pause, not a conclusion.
data-ai
Canonical session close — commit, push, PR, release_task, reflection blocks, handover. Use /dump for emergency bail (no commit/PR/reflection).
data-ai
Emergency session bail — fast resume task + short handover, no commit/PR/reflection. For when you (or the user) need a clean context now. Use /end-session for canonical close.
data-ai
Daily note lifecycle — compose and maintain a factual daily note. Reports the state of the day; does not prioritise or recommend. SSoT for daily note structure.
testing
Launder supervisor/worker task-log output into a Nic-facing narrative — what happened, where things are headed, and what (if anything) is genuinely his to decide. Never relays raw process detail (worker IDs, thread pointers, log paths) or verbatim task-log stream-of-consciousness.