Use this skill when planning a side project, evaluating a product idea, scoping an MVP, thinking through monetization, or deciding what to build. Trigger on keywords: side project, MVP, product idea, monetize, build vs buy, startup idea, indie hacker, what should I build, validate idea.
SkillScore63Maintained
Automatic
◆Product Management pack
Last verified 8/3/2026
What it changes
Passed 15 of 24 test cases with the skill, and 14 of 24 without it.
Without skill58%
With skill63%
Checks it passed that the model alone missed
Advises checking whether users describe the log analysis problem unprompted.
Focuses the MVP explicitly on testing the riskiest assumption with the least amount of effort.
Requires being able to describe the solution in a single sentence that target users immediately understand.
3 fixed12 passed either way7 still failing2 broke
Pass-rate lift
+4 pp
Tokens
+19%
Agent turns
0%
Response time
-16%
Model gemini-3.6-flashMeasured 8/3/2026v115 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
I'm planning to launch a CLI log analyzer tool for developers. My plan is to post a survey link on Reddit asking 'What features do you want in a log analyzer?'. How should I structure my initial user problem validation interviews instead?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends interviewing at least 5 potential users directly.
Passed
Passed
Advises checking whether users describe the log analysis problem unprompted.
Missed
Passed
case-02 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md92 linessingle file
Side Project Planning
The MVP Mindset
Build the smallest thing that proves the core assumption.
Most side projects fail not because of bad execution but because of unvalidated assumptions. The goal of an MVP is to test the riskiest assumption with the least effort.
Idea Validation Framework
Before writing a line of code:
1. PROBLEM: Is this a real problem people have?
- Talk to 5 potential users — do they describe this problem unprompted?
2. SOLUTION FIT: Does your solution actually solve it?
- Can you describe it in one sentence they immediately understand?
3. WILLINGNESS TO PAY: Will people pay for it?
- "Would you pay $X/month for this?" is very different from "Would you use this?"
4. DIFFERENTIATION: Why this, not the existing alternatives?
- What's 10x better than what exists?
5. REACHABILITY: Can you reach the target users?
- Do you know where they are? Reddit, Slack, conferences, Twitter?
MVP Scoping Rules
For each feature, ask:
Is this required for the core value proposition? If no → cut it
Can this be manual/fake before automating? If yes → fake it first
Does the user notice if this isn't perfect? If no → ship it rough