updatelisted

# /slopstop:update Snapshot mid-session progress to the active ticket's tracking files. The ticket stays active (the branch doesn't change). Local-only — never calls JIRA or Linear. ## Project scope (every ticket skill follows this rule) Read `.project-conf.toml` from cwd. Extract `key` (Linear team key, JIRA project key, or GitHub `owner/repo`) and call it `$PREFIX`. Also note `system` (`linear` | `jira` | `github`) for downstream logic. **Only operate on `$PREFIX`'s tickets. The branch-IS-selection parser only matches `$PREFIX-\d+`, so a branch encoding a different project's prefix correctly fails the no-match check.** If `.project-conf.toml` is missing in cwd: stop with `"No .project-conf.toml in cwd. Run /slopstop:gh-init (for GitHub) or create the file manually with system + key."` ## Autonomous mode When `.project-conf.toml` has `[autonomous] enabled = true`, this skill runs unmodified — there are no interactive prompts to skip. `[autonomous]` config keys have no effect on this skill. ## Arguments Optional `$ARGUMENTS`: a ticket key like `BILL-51`. Must match `^$PREFIX-\d+$`. If supplied, use it directly. If empty, fall back to the active ticket parsed from `git branch --show-current`. Explicit ticket keys are useful when updating a paused ticket that no longer matches the current branch (e.g. after a context switch). If `$ARGUMENTS` doesn't match `^$PREFIX-\d+$`: refuse with `"$ARGUMENTS doesn't match this project's prefix ($PREFIX)."` ## Pre-flight - **Re