documentlisted

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.
iansmith/slopstop · ★ 0 · Data & Documents · score 53

Install: claude install-skill iansmith/slopstop

# /slopstop:document Sync the active ticket's local documentation to the ticket on Linear/JIRA. Pure remote sync — does NOT touch local tracking, does NOT change ticket state, does NOT archive. | Local source | Ticket target | |---|---| | `task_plan.md` (whole body) | Ticket **description**, with the prior original description preserved as `## Original description (preserved)` appendix | | `task_plan.md`'s `## Definition of Done` section + evidence | Separate **comment** titled `## Definition of Done — Confirmation` | | `findings.md` (if non-template) | Separate **comment** titled `## Findings (from local tracking)` | Per-artifact safety: if the ticket already has a managed version (recognized by the content signatures above) and its content differs from what would be pushed, the skill stops with a diff report and refuses to push **any** of the three artifacts (all-or-nothing on the remote side). `--force` overrides. `progress.md` is intentionally NOT pushed — per-session diary is too noisy for the durable record. ## Project scope (every ticket skill follows this rule) Read `.project-conf.toml` from cwd. Extract `key` (Linear team key, JIRA project key, or GitHub `owner/repo`) and call it `$PREFIX`. Also note `system` (`linear` | `jira` | `github`) for downstream logic. **Only operate on `$PREFIX`'s tickets. The branch-IS-selection parser only matches `$PREFIX-\d+`, so a branch encoding a different project's prefix correctly fails the no-match check.** If `.project-co