{"slug":"ticket-plugin","title":"ticket-plugin","description":"A Claude Code plugin that keeps a durable per-ticket plan, findings, and progress log for every ticket you work on — without bloating the ticket itself or polluting the repo. Auto-detects Linear or JIRA as your ticket system at run-time.\n\nThe four slash commands form a complete loop around a ticket:\n\n- /ticket-plugin:start <KEY> fetches the ticket, transitions it to \"In Progress\", and seeds task_plan.md, findings.md, and progress.md. Resuming an existing ticket reads back the tracking files and prints a summary.\n- /ticket-plugin:update is a mid-session checkpoint. The ticket stays active.\n- /ticket-plugin:pause snapshots state and clears the active-ticket pointer. Local-only.\n- /ticket-plugin:archive pushes the final task plan back to the ticket as its description and posts findings as a comment, then archives the local folder. Refuses to run unless the ticket is already in a terminal state on the ticket system — the user controls the state transition.\n\nThe aim: fewer wasted tokens re-explaining context between sessions, and a clean ticket-system record of what was actually done by the time you close the ticket.\n\nRequires either the Linear or Atlassian MCP (installable as plugins from anthropics/claude-plugins-official).","developer":"Ian Smith","category":null,"reported_installs":null,"active":true,"first_seen_at":"2026-10-03T22:13:33.942Z","last_seen_at":"2026-11-07T00:08:29.147Z","last_changed_at":"2026-10-03T22:13:33.942Z","platform":"claude","sources":["Community"],"works_with":["Claude Code"],"marketplace_url":null,"repository_url":"https://github.com/iansmith/ticket-plugin.git","web_data":{},"github_data":{},"catalog_sources":{"community":[{"name":"ticket-plugin","source":{"sha":"18a7ab1791a77b6ad57e3f12850eb8a907df7962","url":"https://github.com/iansmith/ticket-plugin.git","source":"url"},"homepage":"https://github.com/iansmith/ticket-plugin","description":"A Claude Code plugin that keeps a durable per-ticket plan, findings, and progress log for every ticket you work on — without bloating the ticket itself or polluting the repo. Auto-detects Linear or JIRA as your ticket system at run-time.\n\nThe four slash commands form a complete loop around a ticket:\n\n- /ticket-plugin:start <KEY> fetches the ticket, transitions it to \"In Progress\", and seeds task_plan.md, findings.md, and progress.md. Resuming an existing ticket reads back the tracking files and prints a summary.\n- /ticket-plugin:update is a mid-session checkpoint. The ticket stays active.\n- /ticket-plugin:pause snapshots state and clears the active-ticket pointer. Local-only.\n- /ticket-plugin:archive pushes the final task plan back to the ticket as its description and posts findings as a comment, then archives the local folder. Refuses to run unless the ticket is already in a terminal state on the ticket system — the user controls the state transition.\n\nThe aim: fewer wasted tokens re-explaining context between sessions, and a clean ticket-system record of what was actually done by the time you close the ticket.\n\nRequires either the Linear or Atlassian MCP (installable as plugins from anthropics/claude-plugins-official)."}]},"manifest":{"url":"https://raw.githubusercontent.com/iansmith/ticket-plugin/18a7ab1791a77b6ad57e3f12850eb8a907df7962/.claude-plugin/plugin.json","payload":{"name":"slopstop","author":{"name":"Ian Smith"},"$schema":"https://json.schemastore.org/claude-code-plugin-manifest.json","license":"CC-BY-SA-4.0","version":"4.0.0","homepage":"https://iansmith.github.io/slopstop/","keywords":["linear","jira","ticketing","productivity","tdd","code-review","agents"],"repository":"https://github.com/iansmith/slopstop","description":"Autonomous, ticket-anchored AI development for GitHub Issues, Linear, and JIRA, built on one idea: stop slop before it goes in, instead of reviewing it out afterwards. Work starts from a ticket, not a prompt. One command drives the whole lifecycle for one ticket or twenty at once, interleaved and unattended: investigate, write failing tests for what the ticket requires (never for what the code already does), prove each one fails for the right reason, attack the plan adversarially, implement without touching the tests, then run three mechanical gates — slop detection, a vacuity check that proves each test would have failed before the branch existed, and a complexity gate — followed by a clean-context review that never sees the conversation that wrote the code. Those gates have no permissive setting: a gate that softens for the cases it exists to police is worse than no gate, because it reports clean. Upstream, :design interviews you into a PRD and :tickets cuts an adversary-approved ticket tree from it. Every stage of every run is recorded to an append-only log — state machine, resume point and timing record in one file, with human waits bracketed so machine time is separable from a weekend away. Six commands and eleven internal workers. More at https://github.com/iansmith/slopstop","displayName":"Slopstop"},"observed_at":"2026-11-06T10:50:12Z"}}