The Learning-Opportunity Command
Turn every confusing moment into an 80/20 lesson aimed at your current skill level
- Difficulty
- Starter
- Time to result
- ~ongoing to results
- Steps
- 3
- Confidence
- 85%
A dedicated slash command that primes the AI to teach — declaring you a 'technical PM in the making' with mid-level engineering knowledge and asking it to explain the current work using the 80/20 rule. Fire it whenever something is hard to understand, so building doubles as deliberate learning instead of blind reliance. Use it alongside the build loop to steadily grow real understanding.
Origin
Because Zevy is non-technical and does 'so much learning,' he built a /learning opportunity command to explain anything he doesn't grasp, calibrated to a technical-PM-in-the-making level and the 80/20 rule.
Core principles
- 01State your current knowledge level so explanations land at the right altitude
- 02Use the 80/20 rule to get the highest-leverage understanding fast
- 03Learn in the moment of confusion, not later
- 04Building and learning should happen together, not sequentially
How to run it
- 1
Trigger on confusion
When something is difficult to understand, run /learning opportunity and name what you want to learn.
Pro tip Use it liberally during peer review and planning whenever a concept isn't fully clear.
- 2
Prime the level and method
The command declares you a technical PM in the making with mid-level engineering knowledge and asks the model to explain the current work using the 80/20 rule.
Pro tip Calibrating the stated level prevents both oversimplified and over-technical explanations.
- 3
Learn from perfect answers
Optionally have the model produce an ideal answer or implementation you can study, learning from a worked example.
Pro tip Zevy used the same 'play the candidate' trick in interview prep to learn from a model answer.
In the wild
When a database or architecture concept was unclear during the workflow, Zevy fired /learning opportunity to get an 80/20 explanation pitched at his level rather than glossing over it.
→ He steadily builds his own sense of how things work instead of relying blindly on the AI.
Common mistakes
Accepting output you don't understand
Shipping code or decisions you can't explain builds dependence and hidden risk; the command exists so understanding grows alongside output.
Is it for you?
Best for
Non-technical builders who want to genuinely learn engineering while they ship
Not ideal for
Experts who already understand the domain and just need execution speed
From the transcript
“I am a technical PM in the making. I have mid-level engineering knowledge. I understand architect uh architecture”
“I want you to explain what we're currently working on uh using the 8020 rule. So this is a great way to learn”
“every time you kind of see something that you don't fully understand, I would definitely use this uh to learn”
From the episode
The non-technical PM’s guide to building with Cursor
Zevi Arnovitz (Meta)