iansmith
Userslopstop is a system for using Claude Code with a ticketing system to have better context with fewer tokens in the context window. It also documents what has been done and concerns about the ticket.
Categories
Indexed Skills (17)
slopstop-gh-init
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.
archive
End the local lifecycle for a ticket: move the local tracking dir from `$TRACKING_DIR/` to `$ARCHIVE_DIR/`. Documentation push (:document) is handled by :merge before archive runs. Does NOT support --force.
create-gh
Create a new GitHub issue and assign it a BILL ticket key that matches the GitHub issue number — so BILL-N always equals GitHub issue
design
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 <topic>.
doc-sync
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.
document
Sync the active ticket's local tracking documentation (task plan, DoD-confirmation evidence, findings) to the ticket on Linear/JIRA. Use /slopstop:document to push or refresh the description + DoD-confirmation comment + findings comment WITHOUT ending the local lifecycle (no archive, no local-dir move, no state change). Idempotent — running it twice on unchanged local state is a clean no-op. Safe by default — if the ticket already has managed documentation that differs from what would be pushed (e.g., someone hand-edited the description), stops with a per-artifact diff explanation and refuses to push anything. --force overrides the divergence check. --dry-run shows what would happen without doing it. Auto-detects ticket system.
merge
Merge PR + advance ticket one state + update tracking files + push docs to ticket + delete branch. Confirms once; shows computed next state. Chains :archive (file move) automatically when the ticket lands in a terminal state after merge. Tells you to run :archive manually for intermediate-state workflows.
plan
Write the active ticket's Plan — Phase 0 red tests, codebase investigation, client-readable DoD, and parallelism-aware work items. Optional [constraint] arg scopes both investigation and plan. Confirms before fanout commit, agent launch, and merge.
pr
PR the active ticket branch — simplify → test → commit → push → create PR → review (CodeRabbit, Greptile, or Claude /code-review). Backend via [pr_review] in .project-conf.toml (default coderabbit). Loops on 🔴/🟡 findings (fix → simplify → commit → re-poll) until clean. ⚪ findings presented for human judgment. Posts a ticket comment linking back to the PR/review once it runs (any backend).
run
Stage 3 of the slopstop process — orchestrate the fleet against a G-tickets-approved ticket tree, launching one hermetically-sealed worktree agent per leaf, integrating blessed work, and stopping at gate G-final. Medium-tier only. Invoke as /slopstop:run <run-id>.
single-ticket
Retrofit an existing ticket to the five-section leaf-ticket standard so it can be handled by :plan --ticket-driven or a fleet run. Interviews toward the missing structure with /slopstop:grill, drafts the five sections, runs the huge-tier adversary loop, then confirms and pushes — preserving the original ticket verbatim below a separator. Interactive only. Invoke as /slopstop:single-ticket <TICKET-ID>.
start
Start or resume work on a Linear or JIRA ticket. Use /slopstop:start <KEY> (e.g. /slopstop:start MAZ-26). Fresh-starts a new ticket (fetches it, transitions to In Progress, asks for a Conventional-Commits-style branch type and creates a feature branch like fix/MAZ-26 or feat/MAZ-26 — with a heuristic suggestion from labels/title and the choice between branching off the default branch vs the current branch when cwd is on a feature branch, plus a "skip" option to opt out of branch creation entirely — then seeds tracking files), or resumes an existing one. Auto-detects ticket system.
tickets
Stage 2 of the slopstop process — read the PRD + charter from the run dir, cut the umbrella/leaf ticket tree per the five-section standard, drive the huge-tier adversary loop over it, and stop at gate G-tickets. Large-tier only. Invoke as /slopstop:tickets <run-id>.
update-ticket
Push the current state of task_plan.md and findings.md to the ticket without archiving locally. Runs /slopstop:update first to checkpoint progress.md, then delegates the push to /slopstop:document. Idempotent — running twice with no changes is a no-op. Auto-detects ticket system.
update
Mid-session checkpoint to the active ticket's progress.md. Use /slopstop:update to snapshot what's been done so far during the same ticket session. The ticket stays active. Local-only — never calls JIRA or Linear.
focus
Mid-session ticket re-tag. Use /slopstop:focus <TICKET> (e.g. /slopstop:focus BILL-201) to re-point this session's router attribution without branch creation or ticket transition. Use /slopstop:focus --clear to reset. Requires [fleet.router] enabled = true.
grill
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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.