Definition & planning sub-skill: Understanding the idea
Turns a raw, one-paragraph idea into a clear problem statement, target user, and success definition, before any research starts.
Claude CodeLast reviewed September 3, 2026
In one minute
- A sub-skill of Definition & planning, invoked first of its four.
- Its job: turn a vague idea into a written problem statement, target user, and definition of success.
- It invokes no sub-skill. Everything it needs to do fits inside one file.
- It asks before it assumes. A skill that fills in the user's answers itself defeats the point of this phase.
SKILL.md
.claude/skills/understanding-of-idea/SKILL.md
yaml
---
name: understanding-of-idea
description: Turns a raw, one-paragraph idea into a clear problem statement, target user, and success definition. Use as the first phase when developing a new digital product, before any research starts.
---
## Ask, do not assume
Ask the user for: the one-sentence version of the idea, who they think has this problem today, and what "working" looks like six months in. Push back if any answer is vague. Do not fill it in yourself.
## Write the output
Save the answers to docs/product/idea.md: problem statement, target user, and success definition, one paragraph each.- The instruction to push back on vague answers is doing real work here. Without it, this skill would happily write a confident-sounding idea.md from three shaky answers, and every later phase reads that file as settled fact.
docs/product/idea.mdis the first file in the chain every later phase reads from. See how phases hand off context.
Where it fits
Invoked by Definition & planning, first of its four sub-skills, before anything else runs. Hands off to Research, which is the next sub-skill to read docs/product/idea.md.
Last reviewed September 3, 2026