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 a work item in this repository's .remit/ work location, and say how far it may go without the practitioner. Use on their words for putting something on the durable surface — "file it", "park this", "an idea", "for the backlog", "new work item", "raise an item", "create a brief for X", "take it to refined", "take it to accepted", "take it all the way" — and on their word that an admitted item takes a further phase. Never to manufacture an item so that something can be started.
remit-resume
Move a work item in this repository's .remit/ work location as far as the practitioner said it may go, and report where it stopped. Use on their words for putting an item back in motion — "pick up X", "carry on with X", "resume it", "unpark it", "run it to refined", "take it to accepted", "take it all the way", "keep going" — and after it stopped or escalated and they have ruled. Use it too on "stop it", "kill it" about a run in progress. Also the one place an ad-hoc check is raised: "check this", "is this any good", "have someone look at this" on work in the conversation.
remit-review
Show the findings still standing against this repository's work items — open or archived — from the record, and on their word have one fresh context attest which of them the code has since fixed. Use when they ask what is standing, in whatever words — "what's standing", "review today's findings", "what did the evaluators leave", "anything still open from last week" — or whether a finding is fixed: "did we fix X", "is that cache header thing still there", "attest".
remit-status
Show what work exists in this repository's .remit/ work location, and rehydrate one item so the practitioner can pick it up. Use whenever they ask where things stand, in whatever words — "where are we", "what's on?", "what's the lowdown?", "anything waiting on me?" — or asks for parked work, or to be caught up on one item: "where did we leave X", "brief me on X", "catch me up on X".
remit-close
Close a work item in this repository's .remit/ work location and archive it whole. Use only on the practitioner's word that the work is over — "close it", "close X", "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 to propose, suggest, or check whether something could be closed.
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".
remit-retro
Turn rulings the practitioner actually made into rubrics in this repository's .remit/rules/ folder. Use only when they call one — "let's do a retro", "retro time", "run a retro", "turn that into a rule", "should that be a rubric?" — and use it then. This is the only door to that folder: no other convention, and no session, proposes a rubric anywhere else.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.