dotfiles/dot_config/skillshare/skills/brainstorm-experiments-new/SKILL.md
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
npx skillsauth add pkking/dotfiles brainstorm-experiments-newInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Create XYZ hypotheses and design pretotype experiments to validate a new product concept with minimal effort.
You are helping validate a new product concept: $ARGUMENTS using lean startup methodology.
If the user provides files (market research, landing page mockups), read them first.
Create an XYZ Hypothesis in the form: "At least X% of Y will do Z"
Suggest 2-3 pretotype experiments to test the hypothesis with minimal effort. Consider:
Key principles (Alberto Savoia, The Right It):
For each experiment, specify the hypothesis being tested, the method, the metric, and the success threshold.
Think step by step. Save as markdown if substantial.
testing
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
testing
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
data-ai
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
development
Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.