← ClaudeAtlas

pushary-chatgptlisted

For ChatGPT and Codex. Plan the work, get the plan approved once, route every decision to the user's phone, and send a push when it is done. Use this whenever a request takes more than one step, contains a choice the user should make rather than you, or will finish while the user is not reading the conversation. In Claude Code, Cursor, Windsurf or Hermes, use the pushary skill instead. Triggers include keep going and ping me when it is done, ask me before you commit to anything, I am stepping away, run this and tell me how it went, and any request where you would otherwise guess at a fork in the road. Every question and answer is recorded, so there is a trail of what was asked and what was decided.
Pushary/pushary-skill · ★ 1 · AI & Automation · score 70
Install: claude install-skill Pushary/pushary-skill
# Pushary: plan first, ask once, always report back Pushary reaches the person on their phone. They answer from the lock screen or from the dashboard, and either way the question and the answer are recorded. That changes how you should work. You no longer have to hold a task open in the chat hoping the user is still reading, and you no longer have to guess at a fork because asking would stall you. Work the loop below. It exists to make the number of interruptions small and the number of unrecorded guesses zero. ## The loop 1. Plan the work and find the decisions before you start. 2. Put the plan to the user as one question. 3. Ask through `ask_user` at every real fork. Never guess. 4. Finish with `send_notification`. ## 1. Plan before you act Before the first action, write out the steps in order and mark the points where you would have to choose. Finding the forks now is the whole efficiency gain. A fork you find while planning can be folded into one question with the others. A fork you find halfway through costs its own interruption, and interruptions are the expensive part. While planning, sort every open point into one of three piles: - **You can answer it.** It is in the request, in the conversation, or derivable from a tool you already have. Answer it and move on. This is not a decision. - **It only matters if a later step goes a certain way.** Leave it. Ask when you get there, if you get there. - **The user has to answer it.** Carry it to step 2 and ask it with