interview me

Data Community

Skill notes

Overview

What people ask for and what they actually want are different things. They ask for "a dashboard" because that's what one asks for, not because a dashboard solves their problem. They say "make it faster" without a number to hit. The cheapest moment to find this gap is before any plan, spec, or code exists. Once you've started building, switching costs are real, and the user will rationalize the wrong thing into a "good enough" thing. The misfit gets locked in.

When to Use

Apply this skill when: The ask is missing at least one of: who the user is, why they want it, what success looks like, what the binding constraint is The request is conventional rather than specific ("build me X", "make it faster") and you can't unpack the convention without guessing You're tempted to start with assumptions you haven't surfaced The user hasn't said which value they're optimizing for when two reasonable ones are in tension (simplicity vs. flexibility, cost vs. speed)

Loading Constraints

This skill needs a live, responsive user. Do not invoke in non-interactive contexts like CI pipelines, scheduled runs, /loop, or autonomous-loop. If you're in one of those and the ask is underspecified, flag that as a blocker for the user instead of guessing.

Step 1: Hypothesize, with a confidence number

Before asking anything, write down your current best read of what the user wants in one sentence, plus an honest confidence number (0–100%): The number forces honesty. If you wrote down a high number but can't actually predict the user's reactions to the next three questions you'd ask, the number is wrong. Start at the confidence level you can defend. When confidence is below ~70%, append a brief reason on the same line — what's still unresolved or missing. This tells the user exactly what the interview needs to surface, and prevents the number from being a vague signal.

Step 2: Ask one question at a time, each with a guess attached

Format: Wait for the user to react before asking the next question. Why one at a time, not a batch: The user can't react to your hypotheses if you bury them in a list Batches encourage skim-reading and surface answers

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@addyosmani · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Hypothesize, with a confidence number

Before asking anything, write down your current best read of what the user wants in one sentence, plus an honest confidence number (0–100%): The number forces honesty. If you wrote down a high number but can't actually predict the user's reactions to the next three questions you'd ask, the number is wrong. Start at the confidence level you can defend. When confidence is below ~70%, append a brief reason on the same line — what's still unresolved or missing. This tells the user exactly what the interview needs to surface, and prevents the number from being a vague signal.

02
Step 2: Ask one question at a time, each with a guess attached

Format: Wait for the user to react before asking the next question. Why one at a time, not a batch: The user can't react to your hypotheses if you bury them in a list Batches encourage skim-reading and surface answers

03
Step 3: Listen for "want vs. should want"

The most dangerous answers are the ones where the user says what a thoughtful answer *sounds like* rather than what they actually want. Watch for: Answers that pattern-match best-practice talk ("I want it to be scalable", "clean architecture") without specifics Answers that defer to convention ("the way most apps do it", "the standard approach") Phrases like "I should probably…", "I think I'm supposed to…", "good engineering practice says…"

04
Step 4: Restate intent in the user's own words

When your confidence is high, write back what you now think the user wants. Keep it tight (5–8 lines), use their language where possible, and structure it so the user can confirm or correct line by line: Including "Out of scope" is non-negotiable. Half of misalignment is silent disagreement about what is *not* being built.

05
Step 5: Confirm — explicit yes, not "whatever you think"

The gate is an explicit "yes." The following are not yes: "Whatever you think is best." → The user is delegating, which means they don't have 95% confidence either. Re-ask with two concrete options framed as a choice. "Sounds good." → Ambiguous. Ask: "Anything you'd refine?" Silence isn't confirmation. "Sure, let's go." → Often a polite exit, not an endorsement. Same follow-up. Silence followed by "okay let's start." → The user has given up on the interview, not converged. Stop and ask whether you've missed something.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.