slopstop
01Plugin Claude Code
Marketplace hosting the slopstop plugin: ticket-anchored AI development for Linear, JIRA, and GitHub Issues — TDD-first planning, scope control, adversarial review, and multi-agent orchestration.
Plugin Claude Code
Marketplace hosting the slopstop plugin: ticket-anchored AI development for Linear, JIRA, and GitHub Issues — TDD-first planning, scope control, adversarial review, and multi-agent orchestration.
Plugin Claude Code
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…
Skill Claude CodeCodex
Release checklist for the slopstop plugin. Use before pushing a version tag, or when adding/renaming a skill (the install shape and the Desktop install script are listed here).
Instructions file
Claude Code instructions for iansmith/slopstop, covering slopstop (ticket-plugin), universal project rules, slopstop-specific declarations, tests (per universal §1) and this repo is the tool the other projects' rules run on.
Agent
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.
Agent
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.
Agent
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.
Agent
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.
Agent
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.
Skill Claude CodeCodex
One adversarial round against a target artifact — attack it for gaps against its stated goals, verify every claim in it against the real repo, and return numbered findings with severity plus a PASS / FAIL / GOAL DEFECT verdict the caller can branch on.
Skill Claude CodeCodex
Push every file in a ticket's tracking directory to the ticket — task plan, findings, the run.jsonl timing log, adversary rounds — so the local record survives where the ticket lives. Bytes move from disk to the backend without passing through the worker. Reports what it pushed; moves nothing and deletes nothing.
Skill Claude CodeCodex
Run the cyclomatic-complexity gate over a branch diff with lizard and return every function at or over the configured warn/reject thresholds — file, line, measured CC, its CC at the base commit, the threshold it broke, and whether the did-not-get-worse exemption applies — plus one overall verdict and a ranked list of…
Skill Claude CodeCodex
Publish drafted tickets to whichever ticket system the project uses — create each issue, assign its key, link parents to children, and resolve cross-reference placeholders. The only place backend-specific creation lives; callers pass a draft and get back a letter-to-key map.
Skill Claude CodeCodex
Stage 1 of the slopstop process — grill the user to shared understanding, then write the PRD and feature charter into the run dir and stop at gate G-design. Huge-tier only. Invoke as /slopstop:design .
Skill Claude CodeCodex
Mirror the design/ directory to the project's ticket-system documentation store (GitHub wiki, Linear Docs). One-way push; design/ files unchanged; orphan pages pruned. Reads .project-conf.toml for the backend. Use /slopstop:doc-sync.
Skill Claude CodeCodex
Run the duplication-check gate over a branch diff with ast-grep and return every clone group at or over the configured min-lines threshold — file, lines, SLOC, hash, scope (intra/cross-file), whether the clone group was pre-existing at the base commit, and a suggested helper signature showing which identifiers vary…
Skill Claude CodeCodex
Bootstrap a GitHub repo for the slopstop ticket workflow. Creates status labels, writes .project-conf.toml. Invoke as /slopstop:gh-init (or /slopstop-gh-init). Idempotent — safe to re-run.
Skill Claude CodeCodex
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use /slopstop:grill to stress-test a plan — typically before breaking it into tickets.
Skill Claude CodeCodex
Implement a ticket's plan until its failing phase-0 tests pass — writes source code, may add tests but never weakens, retargets or removes one, and returns the changes made, before/after test results, and any findings it is reporting rather than fixing.
Skill Claude CodeCodex
Map the codebase for one ticket and return structured investigation findings — relevant modules, entry points, dependencies, conventions to honor, risks, and a predicted file map — as the worker's result, writing nothing to disk.
Skill Claude CodeCodex
Verify that a set of freshly-written tests is pinned to the behavior it names — that a failing test is red for the RIGHT reason, or, under --backfill, that a passing test goes red when the behavior it claims to cover is broken. Returns a per-test verdict with evidence plus one overall PASS / FAIL / PINNED / NOT PINNED.
Skill Claude CodeCodex
Write the phase-0 failing tests that define a ticket's contract before any implementation exists, run them, and return the test files, node-ids, test command, and the observed failure output proving they are red.
Skill Claude CodeCodex
One round of clean-context code review of a diff — find, verify each finding against the real code, apply what survives, report a verdict. Runs in its own forked context so the session that wrote the code never reviews it.
Skill Claude CodeCodex
The single lifecycle entry point — take one or more tickets and drive each through its whole lifecycle (investigate, red tests, adversary, implement, gates, review, PR, merge, archive), interleaving them, launching workers for judgment work and doing every mechanical step inline. Invoke as /slopstop:run [TICKET...].