← ClaudeAtlas

openloops-needs-humanlisted

Use the moment you are blocked on the human and cannot finish on your own: a secret or API key only they can set; a command only they can run (a deploy, a `sudo`, a step your permissions refuse); access you do not have; a purchase, an approval, a decision only they can make; or a decision ALREADY RECORDED -- an ADR, a convention, a default -- that is now in your way or looks wrong given what you now know. Files the blocker as a `manual-task` GitHub issue in the affected repo, carrying a shell predicate, so the obligation outlives the session instead of dying in a message nobody re-reads and `ol owed` can re-check it later. Triggers on: 'I can't do this without you', 'you'll need to run this', 'this needs your credentials', 'blocked on', 'someone has to decide', 'I don't have access to', 'the ADR says X but', or any point where the honest next step is to hand the work back. File it BEFORE writing the hand-back message, not instead of it. Skip when you could do the thing yourself.
thorwhalen/openloops · ★ 0 · Code & Development · score 71
Install: claude install-skill thorwhalen/openloops
# needs-human: file the blocker before you hand the work back When you stop and say "I need you to do X", that obligation exists only in a transcript the human may never re-read, in a session that is about to end. Nothing tracks it. It is found again weeks later, or not at all. A `manual-task` issue is the fix. It is queryable across every repo with one command, from a terminal or a phone, with every session stopped: ```bash gh search issues --owner OWNER --label manual-task --state open ``` And with `openloops` installed, `ol owed` lists the same issues and **re-runs the check each one carries** before showing it — so an ask discharged out of band reads *done* instead of sitting open for months. That only works if you write the check. It is step 5, and it is the field that stops the issue from becoming a lie. So: **the ask goes in an issue first, and in your closing message second.** Two things are not optional and both are easy to skip: - **the verify predicate** — step 5. Without it the obligation can never be observed as finished, only as still filed; - **the egress check** — step 6. Everything you write here lands in a repo that may be public and outlives the context that made it safe. ## When to file File when the next step is genuinely not yours: - a secret, token, API key or credential must be set somewhere you cannot write; - a command must be run that your permissions refuse, or that needs a password, a hardware key, or a browser login; - access must