socratic-questioning
Socratic Questioning coaches developers toward insights using layered questions rather than direct instruction, covering Clean Code principles, GoF design patterns, and architectural trade-offs. It structures discovery through three phases—assess learner level, explore with progressive questions, and consolidate insights—making it ideal for code reviews, design discussions, and principle-based teaching.
Socratic Questioning guides developers to discover solutions through strategic questioning on code principles and design patterns.
AI-generated summary based on this skill's SKILL.md
Install
NickCrew/Claude-Cortex/socratic-questioning · repository language: Python
git clone https://github.com/NickCrew/Claude-Cortex
cp -r Claude-Cortex/skills/socratic-questioning ~/.claude/skills/socratic-questioningFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How can socratic-questioning help teach developers through questions?
socratic-questioning coaches developers toward insights using layered questions rather than direct instruction. Instead of telling developers what's wrong, it structures discovery through three phases: assessing learner level, exploring with progressive questions, and consolidating insights. This approach works across code reviews, design discussions, and principle-based teaching to help teams find solutions themselves.
What's the socratic method for code reviews?
socratic-questioning applies the socratic method to code reviews by conducting learning-focused sessions with guided questions. Rather than pointing out issues directly, it guides reviewers and authors to recognize code smells, Clean Code violations, and design pattern opportunities independently. This transforms reviews from criticism into collaborative discovery, building pattern recognition skills over time.
How does socratic-questioning guide team discovery of design patterns?
socratic-questioning facilitates design discussions using strategic questioning to help teams discover GoF patterns and architectural trade-offs themselves. It layers questions to progressively deepen understanding—starting with context, moving through trade-offs, and ending with principle consolidation. This discovery-based approach trains developers to recognize patterns and principles independently across future projects.
Can socratic-questioning coach developers on Clean Code without telling answers?
Yes. socratic-questioning is built on coaching developers without telling them answers. It uses questioning techniques to guide developers toward recognizing Clean Code principles, refactoring opportunities, and design improvements through their own reasoning. The three-phase structure—assess, explore, consolidate—ensures learners internalize principles rather than passively receiving instruction.
What learning outcomes does socratic-questioning deliver?
socratic-questioning develops pattern recognition, independent problem-solving, and principle-based thinking. Developers learn to identify code smells, evaluate architectural trade-offs, and apply Clean Code and GoF patterns through guided discovery. By consolidating insights through questioning rather than instruction, teams build lasting understanding and coaching capability for future design challenges.
Is socratic-questioning suitable for design discussions?
socratic-questioning is ideal for facilitating design discussions. It structures conversations through strategic questioning to explore trade-offs, surface assumptions, and guide teams toward sound architectural decisions. The socratic method keeps discussions learning-focused, ensures all voices contribute to discovery, and builds shared understanding of design principles and patterns.
SKILL.md
rendered from the published skill — quoted content, verbatim
Socratic Questioning
Guide developers toward discovery through strategic questioning rather than direct instruction. Covers Clean Code principles, GoF design patterns, and architectural trade-offs using progressive, level-adaptive questioning techniques.
When to Use This Skill
- Coaching developers on Clean Code or design pattern concepts
- Facilitating design discussions where the team needs to discover trade-offs
- Helping developers identify code smells and refactoring opportunities
- Teaching programming principles through guided discovery
- Running code review
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 3 files
skills/socratic-questioning/SKILL.md
skills/socratic-questioning/references/facilitation-patterns.md
skills/socratic-questioning/references/questioning-techniques.md