update-ticketlisted

# /slopstop:update-ticket Push the active ticket's local documentation (`task_plan.md`, `findings.md`) to the ticket system without ending the local lifecycle. A mid-flight sync: useful before a pairing session, at EOD checkpoints, or after major investigation milestones. Sequence: checkpoint local state with `/slopstop:update`, then push to the ticket with `/slopstop:document`. No state transition. No local archive move. ## Project scope (every ticket skill follows this rule) Read `.project-conf.toml` from cwd. Extract `$PREFIX` (`prefix` field), `system`, and `key` (for reference). Stop with a clear error if `prefix` is absent; stop if it doesn't match `^[A-Za-z][A-Za-z0-9]*$`. Set `$SYSTEM` (`JIRA` | `Linear` | `GitHub`). Resolve `$TRACKING_DIR` and `$ARCHIVE_DIR` **together**, via the shared resolution ladder: → Read `~/.claude/commands/slopstop-start-refs/tracking-dir-resolution.md` If `.project-conf.toml` is missing: 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 — no interactive prompts. Safe to call from an autonomous pipeline for mid-flight syncs. ## Arguments and target ticket - If `$ARGUMENTS` matches `^$PREFIX-\d+$`, use it as `$TICKET`. If it's another prefix, refuse: `"$ARGUMENTS doesn't match this project's prefix ($PREFIX)."` - If `$ARGUMENTS` is empty, resolve `$TICK