---
name: get-clarity
description: Interview the user until they reach clarity on a decision, plan, or problem, then summarize the breakthrough and next steps, optionally saved as a decision record. Use when the user says "help me get clarity", "I'm stuck", "help me think through X", or is going in circles.
---

# Get Clarity

Interview the user until they reach a breakthrough. The core move is WAYRTTD: **What Are You Really Trying To Do?** — most stuckness is solving the wrong problem, so probe beneath the stated problem for the real goal.

## How to Interview

1. **Frame:** Restate the topic in one sentence. Then ask WAYRTTD with the host's structured question tool when available, or as a concise plain-text question otherwise. Offer the stated goal plus a few plausible deeper goals as options.
2. **Ask in rounds:** Ask only what the next step needs; don't batch a questionnaire. When structured choices are supported, give concrete options and mark your best-judgment pick "(Recommended)" with a one-line reason. Otherwise ask the same choices in compact prose. Rotate angles as needed: goal, constraint, stakes, reversible experiments, and resistance.
3. **Reflect between rounds:** Briefly name patterns and contradictions you're hearing.
4. **Stop at the breakthrough:** When answers get decisive or the user says "oh — actually...", stop asking. If the conversation starts repeating without new information, take a position instead ("I'd do X — here's why") and ask them to react.

## Wrap Up

Summarize in chat: **The Breakthrough** (the WAYRTTD answer + the insight) and **How to Proceed** (concrete next steps, smallest first).

Offer to save it as `decision_<name>.md` when the decision will shape later work or they'll want to remember why. Record the date, the decision, why (the breakthrough), the options considered and why they lost, what would make you revisit it, and the next steps. Save it where the user says. In a project, otherwise use the existing planning folder (`plans/`, `specs/`, or `docs/specs/`) or create `plans/` at the project root; outside a project, use the current directory. Don't overwrite an existing decision; choose a distinct name.

Then recommend a next step: `brainstorm` if the decision is to build something still loosely defined, `create-spec` if it's already clear, or just starting on step one. Continue only when the user says so or asked for it up front.

## Guidelines

- Be a thinking partner with opinions, not a survey — always recommend.
- Follow the energy: dig into surprising answers even if it breaks the script.
- Challenge premises: "do you actually need to X at all?" is often the best question.

Text supplied with the invocation is the initial topic.