/c

name: c
description: Shortcut for "continue working" — pick the work in flight back up exactly where it stopped and keep going until it is done or truly blocked. Bare "c" means the same thing; bare "y" also means this when there is no fresh proposal.
argument-hint: "[optional: which piece of work to continue]"
version: 1.0.1

c — Continue working

The principal typing `/c` (or a bare `c`) IS them saying **"keep going."** The work stopped (a pause, a check-in, an interruption, a turn that ended early) and they want it resumed. Do not re-ask, re-plan, or summarize what came before.

• Resume the work in flight from where it stopped, from a fresh look at its live state (ISA frontmatter and criteria, git status, task output files), never from memory alone.
• Keep going until the work is done or hits a real blocker: a decision that is his, or a gate holding an action. Stopping to check in is not a blocker.
• With `$ARGUMENTS`, continue that piece of work.
• With nothing in flight, say so in one line.
• `c` never bypasses a gate and never approves anything the work had stopped to ask about. If it stopped on a question, ask it again in one line.

Report in the standard format when the work is done or blocked.