intuitive-interviewing

A context-aware interview workflow for gathering and refining requirements with a user. It adjusts the level of detail, avoids repeating known information, drafts an early outline, and notices when the request changes direction.

In plain words
What is it for?
Use it when building or refining a skill, spell, or other workflow through conversation. It is also for any user-facing interview where requirements need to be collected.
Why use it?
It reduces unnecessary questions and keeps requirements interviews focused. It also helps ensure the final specification contains the required information.

Skill for Claude CodeCodex

Part of the wizard plugin — 37 skills, 6 commands, 1 agent, 1 hook shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/redhuntlabs/wizard/intuitive-interviewing
Any agent
npx skills add redhuntlabs/wizard --skill intuitive-interviewing
Clone the repo
git clone --depth 1 https://github.com/redhuntlabs/wizard

Made for: Claude Code, Codex.

Or install wizard, the plugin that ships this one along with the rest of its 37 skills, 6 commands, 1 agent, 1 hook.

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,491 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.01491
Opus 5 $0.00023 $0.00745
Sonnet 5 $0.00009 $0.00298
Haiku 4.5 $0.00005 $0.00149

Measured 3d ago against content hash 2e3fe412cbdb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

intuitive-interviewing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/intuitive-interviewing/SKILL.md · 166 lines

How it starts

The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Intuitive Interviewing

What this does

Turns a 12-phase interview into a context-aware conversation. Detects what the user already said, picks the right depth, matches against known workflow shapes, drafts a strawman early, and pivots when scope shifts.

When to use

  • Inside building-a-spell (Stage 1)
  • Inside refining-a-spell (when capturing what changed)
  • Anywhere a user-facing requirements interview happens

What you bring (Inputs)

A context dictionary from the calling skill, containing whatever was already extracted (from the user's trigger phrase + any prior turns).

What you get (Output)

A filled interview: every required frontmatter field has a value, every required body section has content, plus any kind-specific extras.

How it works (Steps)

This is a workflow with explicit stages and gates.

Stages

Stage A: Pick depth

Inspect the context dictionary. Pick depth as follows:

If... Use depth
User explicitly said "quick", "simple", "just" Express
Context dictionary has 4+ extracted fields already Express
Kind is discipline Deep (always)
User is first-time (no $WIZARD_HOME content) Standard
Otherwise Standard

Allow user override: "Tell me which depth you'd like (express / standard / deep)" — but only if depth was ambiguous.

Output handed to next stage: chosen depth.

Stage B: Match against workflow shapes

Read all shapes under skills/building-a-spell/workflow-shapes/. Score each by overlap of:

  • Trigger keywords vs context dictionary's name and description
  • Output type vs context dictionary's output
  • Step count and shape

If top score >= 0.7, propose it as a strawman:

"This looks like a <shape-name>. Here's a draft. What would you change?"

If top score < 0.7, skip to Stage C.

Output handed to next stage: strawman draft (or none).

Read the full file on GitHub · 166 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 166 lines · 47 tokens per session scan A 2e3fe412cbdb

Subscribe to this mod's changes

intuitive-interviewing is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 1,491 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.