prompt-refinerlisted

# Prompt refiner > **Announce on activation:** "Using prompt-refiner — I'll confirm scope before executing." The cheapest place to fix a misunderstanding is *before* the work starts. This skill is a 30-second gate, not a ceremony. ## Process 1. **Classify intent.** Is this a fix, a feature, a review, research, or a question? If two or more at once, that's a sign the request needs splitting. 2. **Spot the ambiguity — and don't trust the premises.** What's missing that changes what you'd build — scope, target files, expected output, constraints, the definition of done? If the request asserts "X already does Y" or names a file, grep/read to **verify the claim** first — a confident wrong premise is the most expensive ambiguity. 3. **Decide the path by clarity (a 4-tier scale):** - *Crystal* → restate it in one line and proceed (no friction). - *One missing piece* → ask exactly one focused question, then proceed. - *Several intents / wide-open scope* → propose a concrete interpretation (scope + acceptance criteria) and get a yes before building. - *Claims-heavy or high-stakes* → **grill mode**: interview one focused question at a time, verifying each load-bearing claim against the code, until the spec is airtight. 4. **Restate, don't expand.** The rewrite must preserve the original intent — never quietly add scope the user didn't ask for. Shorter and sharper, not longer. ## Output shape ``` Intent: <fix | feature | review | research | que