Catalog/Intuition Hypothesis Test

Intuition Hypothesis Test

Make sure to use this skill whenever a product decision is justified by gut feeling, a senior leader has a strong opinion but the reasoning is implicit, a debate is stuck because both sides argue from intuition, a feature is being championed without data, or the team needs to convert a hunch into something testable — even if the request is about 'decision-making' or 'product strategy' rather than explicitly about testing intuitions.

Lenny's Podcastengineeringadvisorprocedural
Download .skillInstall instructions

Install

Run the one-liner to fetch and unpack the skill into your Claude Code skills directory:

curl -sL https://skill.broker/skills/dylan-field/intuition-hypothesis-test.skill -o /tmp/intuition-hypothesis-test.skill && \ unzip -o /tmp/intuition-hypothesis-test.skill -d ~/.claude/skills/intuition-hypothesis-test/

Manual install

Download the .skill file above, then unzip it into ~/.claude/skills/intuition-hypothesis-test/.

Related skills

Ai Deployment Flywheel Free
Make sure to use this skill whenever deploying an AI agent or model into production and the team expects it to work perfectly on day one, evaluating an AI vendor that claims 'one-click deployment,' or designing the data-feedback loop that makes an AI system improve post-deployment — even if the request is about 'AI deployment' or 'agent design' rather than explicitly about flywheels.
engineeringadvisorheuristicAishwarya Naresh Reganti Kiriti Badam
Trust Battery Check Free
Make sure to use this skill whenever a working relationship seems strained, decisions are being second-guessed without clear rationale, collaboration between two parties is degrading, a new partnership needs a baseline trust assessment, or delegation levels need calibration — even if the request is about 'collaboration' or 'working relationships' rather than explicitly about trust.
engineeringadvisorheuristicBrandon Chu
Artifact Driven Debate Free
Make sure to use this skill whenever a product debate has lasted more than 2 meetings, participants argue from different mental models with no shared reference, a design or architecture decision needs convergence, the team is going in circles with abstract arguments, or a decision requires comparing approaches side by side — even if the request is about 'decision-making' or 'alignment' rather than explicitly about artifacts.
engineeringadvisorproceduralDylan Field