shobman
UserKeep practitioner-directed AI work in Git. Decide what starts, what stops, who builds it, who judges it, and when it leaves your attention.
Categories
Indexed Skills (12)
capture-work
Capture a new work item as a brief, open a further phase on an item already admitted, or park/activate an existing one, in this repository's .remit/ work location. Use whenever the practitioner signals work they want kept but not started — "create a brief", "new work item", "raise an item", "an idea", "future item", "dump this new item: ...", "we should eventually ..." — or asks to park, shelve, pick up, or activate an item, or rules that an admitted item takes another phase — "next phase is the build", "open a second phase for that". Use it whenever the practitioner admits something durable; never to manufacture an item so that work can start.
close-work
Close a work item in this repository's .remit/ work location and archive it whole, when the practitioner directs it. Use only when they say the work is over — "close it", "close <item>", "that's finished, archive it", "we're not doing this, drop it", "abandon it" — and use it then, including for work that shipped nothing. Never invoke this to propose, suggest, or check whether something could be closed.
dispatch-work
Send a bounded, isolated worker to carry out authorised work in this repository — briefed from an active item's brief, from that item's current phase, or from the outcome and boundary established live when there is no item — returning a pull request. Use whenever the practitioner directs that work be carried out by someone other than you, in whatever words — "send a worker on it", "put someone on this", "get it built", "dispatch it", "have an agent do X", "go build <item>" — and whenever isolation, a particular model, elapsed time, or keeping this context clean makes a worker the right means. Carrying the work out yourself is equally valid and needs no dispatch.
evaluate-work
Have AI-produced work judged by a fresh context that did not author it. This happens by default for work produced for the practitioner's acceptance — skipped only when the practitioner has asked to skip it or delegated a policy saying otherwise, never on your own judgment of proportionality. Use before asking the practitioner to accept AI-produced work, when they ask for work to be checked, verified, reviewed, or assessed independently — "get it verified", "have someone check it", "is this any good", "evaluate the PR" — and to send a must-fix back to a builder and have the changed work judged again. Record the verdict with the work item where one exists.
resume-work
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".
remit-new
Admit or park practitioner-directed work, or open a phase they authorise. Use for "file it", "park this", "new item", "create a brief", "take it to refined", "take it to accepted" or "take it all the way". Keep intake problem-first and ask only what is missing to make the outcome judgeable.
remit-resume
Resume an item as far as authorised and report its terminal state, cause and next required action. Use for "pick up X", "carry on", "resume", "unpark", "run it to refined", "take it to accepted", "take it all the way" or a ruling after a stop. Also use for stopping a running chain and for an explicitly requested ad-hoc check.
remit-review
Show standing findings and their present disposition, or on request attest whether code has fixed them. Use for "what is standing", "review today’s findings", "anything still open", "did we fix X", "is that still there" or "attest".
remit-status
Show the board or catch the practitioner up on an item: current outcome, state, blocker and decision owed. Use for "where are we", "what is on", "anything waiting on me", parked work, "where did we leave X", "brief me on X" or "catch me up on X".
remit-retro
On a called retro, examine actual practitioner rulings and propose one compact batch of additions or pruning, routing each lesson to its useful home. Use for "retro", "turn that into a rule" or "should that be a rubric". Rubric changes require the practitioner’s ruling.
remit-close
Close and archive an item on the practitioner’s word: "close it", "archive it", "drop it" or "abandon it", including work that shipped nothing. Explain material closure consequences and act on existing authority.
remit-exposure
Report this repository's recorded exposure — the words the practitioner said and the words they were told, per channel, never summed. Use when they ask "how much have I said today", "exposure", "what's this session cost me", "where am I today", or the same numbers for one item or session, or the movement over time — "am I taking on more", "how many items am I carrying", "the trend".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.