CodexPluginStats
← Claude plugins
CLAUDE PLUGIN

ticket-plugin

Ian Smith v4.0.0

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...

Create a free account to save this plugin.

From the developer

License

CC-BY-SA-4.0

Works with

Claude Code

Description

From the marketplace listing

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. The four slash commands form a complete loop around a ticket: - /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. - /ticket-plugin:update is a mid-session checkpoint. The ticket stays active. - /ticket-plugin:pause snapshots state and clears the active-ticket pointer. Local-only. - /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. The 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. Requires either the Linear or Atlassian MCP (installable as plugins from anthropics/claude-plugins-official).

Source repository ↗ Website ↗

What changed

No changes recorded yet. Follow this plugin to keep track of future changes.

Keywords

Files & skills

ticket-plugin · catalog manifest

Saved declaration

{}
ticket-plugin · catalog manifest

Saved declaration

{
  "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)."
}
slopstop · catalog manifest

Saved declaration

{
  "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"
}

plugin.json observed Nov 6, 2026 · 10:50 UTC. Manifest source ↗

Catalog declarations and available plugin.json metadata are saved. Referenced skills and executable source files are not downloaded or tested. Missing components in a manifest do not prove that the plugin has none.

Installation instructions

Community

/plugin marketplace add anthropics/claude-plugins-community
/plugin install ticket-plugin@claude-community

Claude Code installation documentation

Technical details
Sources
Community
First seen
Oct 3, 2026 · 22:13 UTC
Last seen
Nov 7, 2026 · 00:08 UTC
Latest observed change
Oct 3, 2026 · 22:13 UTC
Collection status
Listed
Reported installs
Not provided

Installation counts are source-reported, not independently verified active users. Observation dates are not release dates.

Download plugin data (JSON)

Plugin history: freshly prepared. Prepared . Refreshed when catalog data changes or after 6 hours. Your account and Follow status are live.