Anytime

/get-clarity

Find what you’re really trying to do.

Install this skill Read the skill

When to use it

You’re stuck, or going in circles.
You need to think through a decision, plan or problem.
You suspect you’re solving the wrong problem.

How it works

The stated problem what you came in with
WAYRTTD? What are you really trying to do?
Rounds of options goal, constraint, stakes, reversible experiments, resistance
The real goal “do you actually need to X at all?”
The breakthrough “oh, actually…”

1 Frame
Restates the topic in one line, then asks WAYRTTD: your stated goal plus a few deeper ones.
2 Ask in rounds
Only what the next step needs. Concrete options, one marked (Recommended).
3 Reflect
Names the patterns and contradictions it’s hearing. Then rotates the angle.
4 Breakthrough
Answers turn decisive, or “oh, actually…”. Going in circles? It takes a position.
5 Wrap up
The Breakthrough and How to Proceed, smallest step first.

What you get

A decision in chat; optionally decision_<name>.md.

In chat, every time

The Breakthrough: the WAYRTTD answer and the insight.
How to Proceed: concrete next steps, smallest first.

decision_<name>.md

optional, when the decision shapes later work

Date
The decision
Why: the breakthrough
Options considered, and why they lost
What would make you revisit it
Next steps

Next step

When it’s done, /get-clarity recommends one of these:

/brainstorm · build something still loosely defined
/create-spec · what to build is already clear
Start on step one · the smallest next step

Install /get-clarity

One prompt installs just this skill. Want the whole system? Install all five from the Planning System page.

Then paste it into a conversation with your agent.

Works with

Claude Code
Codex
Grok Bot

Download get-clarity.zip Unzip into your agent’s skills folder.

Read the installation prompt

Install the get-clarity skill from this manifest for use in the agent I am using now:
https://ainativebuilder.com/plan/resources/get-clarity/manifest.json

Identify this agent and use its supported personal/global skill installation or saved-skill mechanism, so the skill is reusable beyond the current project or conversation. If the correct mechanism is unclear, check this agent's official instructions before proceeding.

Fetch the manifest and download every listed file from the same origin. Preserve the exact contents and relative references of all 1 Markdown file, keeping each skill in its own folder named after the skill. Stage the complete bundle and verify its SHA-256 hashes before installation. If a download or hash check fails, stop and report it without changing existing skills. Back up any existing same-name skills before replacing them; keep filesystem backups outside skill-discovery directories. Install independent copies, not symlinks.

Verify that the skill is saved and discoverable and that every referenced template is accessible. If this host cannot preserve the complete bundle, explain the limitation instead of claiming successful installation. Report any enablement or refresh step still needed.

Confirm what was installed and where, then stop. Do not invoke the skill, start an interview, plan a project, or implement anything.

Install all five skills instead

Full instructions

Read each complete file below. Copy or download the original Markdown to use with your agent.

Get clarity skill

get-clarity/SKILL.md

Select and copy the complete source below.

---
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.

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

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.
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.
Reflect between rounds: Briefly name patterns and contradictions you’re hearing.
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.

When to use it

How it works

1 Frame

2 Ask in rounds

3 Reflect

4 Breakthrough

5 Wrap up