ask-me · git:20261111.7bcdfe9 · 2026-11-11 · sha256 fcdebe3215bdc83a
ask-me git:20261111.7bcdfe9A
Immutable. This exact content never changes and is served at /api/v1/blob/fcdebe3215bdc83a.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7mm2k2opasylalrp/fcdebe3215bdc83a23f31bec155b612f00a0ad2dc6a442ee23fe89f84fa3481f.json
Then /plugin install ask-me@markdownregistry-7mm2k2opasylalrp in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: ask-me description: Find the open decisions in the current context that need the user, ask only the ambiguous, critical, or hard-to-reverse ones with recommendations, and record the answers for later skills such as write-plan. Use on explicit invocation. metadata: origin: custom --- # Ask Me Align with the user before later work starts. Find the decisions in the current context that need the user, ask only those, and record the result in the conversation. Later skills, such as write-plan, read this record as conversation context. Do not start the later work, and do not change files or external state. Use judgment for scope, number of questions, format, and follow-up. These rules set the bar for a question, not a fixed procedure. ## Find the open decisions Use the conversation, supplied material, repository instructions, and the code. Investigate read-only only as far as necessary so that you do not ask what the context or the code already answers. Identify the decisions that the intended work depends on. Make a decision yourself when the context, conventions, or evidence support one option, or when a wrong choice is cheap to correct later. Prefer a reasoned decision to a question. Ask the user only when one of these conditions applies: - The context does not resolve the decision, and a wrong choice materially changes scope, acceptance, cost, risk, or authority. - The decision is very difficult or expensive to reverse, for example data loss, migrations, public interfaces, external commitments, or removal of behavior that people rely on. A clear recommendation does not remove the need to ask. Ask, and give the recommendation. Do not ask about facts that you can find, routine implementation details, choices that the later work can make with better evidence, preferences with no material effect, or what the user already said. ## Ask Use the harness's user-input tool when one is available. Otherwise, ask in the response and stop. Make each question stand alone: give the necessary context, the options when they help, your recommendation and its reason, and consequences that are not obvious. Ask follow-up questions only when an answer opens a new decision that meets the same bar. If no decision meets the bar, say so in one line, record your material decisions, and stop. ## Record After the user answers, give a concise record that later skills can use: - **Your decisions:** the meaning of each answer and the constraint it sets. An answer that changes scope is a requirement update. - **Agent decisions:** the material decisions that you made, each with a short reason. These are proposals, not user approval, until the user adopts them. The user can override any of them. - **Open:** decisions that are still open, and the assumption that later work uses until the user decides. Keep the record in the conversation. Write it to a file only when the user asks. Then stop. The user starts the next skill.