Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Interview the user relentlessly about a plan, project, workflow, or design until you reach shared understanding. Make sure to use this whenever the user wants to be grilled, stress-test an idea, clarify a new project, surface missing context, or think through decisions before execution.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-08 | ✗→✓ | ▲ Improved | -35% | 0% |
| case-11 | ✗→✓ | ▲ Improved | -62% | 0% |
| case-14 | ✗→✓ | ▲ Improved | -48% | 0% |
| case-02 | ✓→✗ | ▼ Worse | -56% | 0% |
| case-16 | ✓→✗ | ▼ Worse | -62% | 0% |
Interview me relentlessly about every important aspect of this plan until we reach a shared understanding.
Walk down each branch of the decision tree, resolving dependencies one by one. For each question, provide your recommended answer, but stay open to correction.
Ask questions one at a time.
If a question can be answered by exploring the codebase, existing docs, available memory, or context already present in the session, explore that first instead of asking me to repeat it.
When relevant, begin by identifying what kind of project this is and what context already exists. Distinguish between:
Do not depend on any specific file path or agent harness. Use whatever context is available in the current environment. If important context is missing, ask me to provide it.
As the discussion progresses, periodically checkpoint the emerging understanding in a lightweight way. Keep track of:
Keep the process lean. Do not turn this into a giant framework or a long lecture. The goal is to uncover the missing context that will make downstream execution much stronger.
Stop when the important branches have been covered and there is a solid, practical shared understanding. Finish with a concise synthesis of:
Other measured skills in the registry, with their headline benchmark lift.