← ClaudeAtlas

resume-worklisted

Show what work exists in this repository's .remit/ work location, and rehydrate one item so the practitioner can resume it. Use whenever they ask where things stand, in whatever words — "where are things at?", "what's happening in here?", "what's the status of my work items?", "where are we at?", "what's the lowdown?", "what's on?" — or ask to see parked work, or to rehydrate, restore, or be caught up on an item — "rehydrate it", "where did we leave X", "brief me on X", "catch me up on X".
shobman/remit · ★ 0 · AI & Automation · score 72
Install: claude install-skill shobman/remit
# Resume The practitioner has been away, possibly for weeks, and is carrying none of this in their head. Give them the calm view. When they pick an item, tell them where it stands from what is written and what is shipped — then ask what they want to do. Nothing here starts, ranks, or revives work. ## Show them the view ```sh sh "$(git rev-parse --show-toplevel)/bin/remit" list ``` That is active work only, one line per item: slug, then title. Report it plainly — no commentary on which matters more, no suggestion of where to begin. If it says there are no active items, say so and stop there; do not go looking for something to fill the silence. Parked work exists but is dormant. Show it **only** when they ask for parked, shelved, or "the rest": ```sh sh "$(git rev-parse --show-toplevel)/bin/remit" list --parked ``` If `remit` warns on stderr that an item was not listed, pass that on — an unreadable item is a thing they need to know about, not a thing to quietly fix. ## Rehydrate the item they pick Rehydration is reading, not reconstruction. Read three things and nothing else: 1. **the work item** — `.remit/<slug>/brief.md`, including its Phases section and current-phase line where it runs in phases, and every other file kept with it: the phase files, the evaluation record, whatever else is there; 2. **the authoritative content the brief links to** — the linked files, or a URL if this harness can reach it; 3. **the current code** — what is actually in the repo