startlisted

# /slopstop:start Start or resume work on a ticket. **On fresh-start:** transitions the ticket to In Progress, creates a feature branch named `<type>/<TICKET-ID>` (e.g. `fix/MAZ-99`, `feat/MAZ-99`) — `<type>` is a Conventional-Commits-style prefix chosen interactively, with a heuristic suggestion when one can be inferred from the ticket's labels or title; a `skip` option opts out of branch creation entirely — and seeds tracking files at `~/.claude/ticket-active/<TICKET>/`. If cwd is on a feature branch (not the repo default), the skill warns and asks whether to branch off the default branch or off the current branch. **On resume:** reads the tracking dir, prints a summary, appends a session header. No ticket-system call, no git. Auto-detects ticket system (JIRA via Atlassian MCP, or Linear via Linear MCP). ## 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 `[auton