From corneliu-skills
Refine questions and problems through 7 Socratic lenses to improve thinking, AI interactions, and decision-making. Use this skill when the user wants to ask better questions, refine a question, think through a problem from multiple angles, explore an idea, challenge their thinking, apply Socratic questioning, use the 7 lenses framework, stress-test a decision, or generally improve the quality of a question before asking it. Also use when the user seems stuck on a decision or is asking a surface-level question that would benefit from deeper exploration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/corneliu-skills:ask-better-questionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform shallow questions into powerful ones by running them through 7 Socratic lenses.
Transform shallow questions into powerful ones by running them through 7 Socratic lenses.
Take the user's question or problem and apply the 7 lenses:
Example:
User's question: "How do I build better retention?"
After 7 lenses:
Pick 1-2 that resonate. Ask those instead. Get better answers.
| Lens | Reframes | Best for |
|---|---|---|
| Challenge | Weaknesses in your approach | Catching blind spots |
| Unconstrained | What's truly wanted, not constrained | Vision-setting, discovering what matters |
| Meta | What you're missing | Completeness checks, edge cases |
| Uncertainty | Admitting what you don't know | Risk awareness, intellectual humility |
| Inverse | Opposite direction | Discovering root causes, hidden assumptions |
| Reframe | Fresh perspective from another field | Novel solutions, pattern recognition |
| Assumptions | What you're actually optimizing | Alignment checks, goal clarification |
For detailed guidance, prompts, and examples for each lens, read references/lenses.md.
Surface: "Should I hire more engineers?"
Lens 1 (Challenge): "What are the real constraints on our output — is it headcount?"
Lens 4 (Uncertainty): "Where am I wrong about engineering capacity?"
Lens 7 (Assumptions): "Am I optimizing for velocity or code quality?"
Ask these 3 instead of the surface one.
Stuck on: "Do I pursue this project or not?"
Lens 6 (Reframe): "How would a CFO see this? A designer? A customer?"
Lens 5 (Inverse): "What if I actively avoided this? What's the fear?"
Lens 3 (Meta): "What am I not asking that would help?"
Run through these lenses first; the decision often clarifies.
Brainstorming: "How do we improve onboarding?"
Lens 5 (Inverse): "How would we maximize onboarding failure?"
Lens 2 (Unconstrained): "What if onboarding took 10x longer but was perfect?"
Lens 6 (Reframe): "How would a game designer think about this?"
These unconventional angles unlock creative solutions.
Trio for clarity:
Trio for creativity:
Trio for risk:
npx claudepluginhub corneliu-iancu/skillsCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.