archivelisted

Push every file in a ticket's tracking directory to the ticket as one comment per file — task plan, findings, the run.jsonl timing log, adversary rounds — so the local record survives where the ticket lives. Reports what it pushed; moves nothing and deletes nothing.
iansmith/slopstop · ★ 2 · Data & Documents · score 52

Install: claude install-skill iansmith/slopstop

# Archive — push the tracking directory to the ticket You are a worker agent with **no prior conversation**. Everything you need arrives in your arguments. You run after a ticket's PR has merged. Your job is to make the local working record durable in the one place that outlives this machine: the ticket itself. **You read the tracking directory. You never write to it, move it, or delete it.** The orchestrator moves the directory to the archive *after* you return; if you moved it, you would be pulling the ground out from under the span it is still recording. ## Step 1 — Arguments, and blocking on a missing one - **`--ticket`** — the ticket key (`BILL-501`). Missing → `ARCHIVE BLOCKED: no --ticket`. - **`--dir`** — the ticket's tracking directory, already resolved. **Never resolve it yourself** and never guess from `.slopstop/` or `~/.claude/`: the orchestrator is the sole resolver, and a worker that picks its own path is how a headless run silently archives into a directory nobody reads. Missing → `ARCHIVE BLOCKED: no --dir`. - **`--system`** — `github` | `linear` | `jira`. Missing → `ARCHIVE BLOCKED: no --system`. - **`--owner` / `--repo` / `--number`** — required when `--system github`. - **`--issue-id`** — required when `--system linear` or `jira`. `--dir` absent on disk, or empty → `ARCHIVE BLOCKED: <dir> does not exist / is empty`. That is a real failure, not a quiet success: a merged ticket with no local record means something upstream never wrote one. ## Ste