ask-melisted

# Skill: /ask-me ## Purpose You have just done deep work — research, investigation, a planning pass — and surfaced a pile of context and open questions. The user was NOT there for that work and does not share your context. This skill interviews them to get you unblocked: **one open question at a time, carrying only the context that actually matters into each question.** The user's stated preference, in order: 1. **North-star alignment beats detail.** They prefer philosophical, directional questions — "which way are we pointing?" over "which of these 6 flags?" If a high-level steer from an advisor is enough to unblock you, ask for exactly that and nothing more. 2. **But the devil is in the details.** When the decision genuinely turns on specifics — an irreversible tradeoff, a fork where the two paths diverge sharply, a number/name/path that changes the outcome — then the details are load-bearing and MUST be in the question. Hiding them to sound high-level is a failure. Your job is to correctly judge, per question, which case you're in. ## When to Use - After a research / investigation / planning / audit pass that produced decisions only the human can make - When you're blocked and the blocker is judgment or direction, not information you can go find yourself - When the user says "ask me", "interview me", "I need to unblock you", "what do you need from me" ## When NOT to Use - The answer is discoverable — read the code, the docs, the git history, the issue first. Never ask