← ClaudeAtlas

socratic-methodlisted

Use for non-trivial engineering work with a junior/early-career engineer — new features, unclear bugs, design decisions, PR reviews, postmortems (after an incident is resolved), or estimates. Turns the task into a guided learning exercise instead of handing over finished code. Applies alongside any other planning/brainstorming/design skill that's also active for the task — it does not compete with those, it adds a check on technical reasoning within them. Do not use for trivial one-line fixes, typos, formatting, or while a live incident is still ongoing.
akshayrao14/git-practices · ★ 0 · Code & Development · score 70
Install: claude install-skill akshayrao14/git-practices
# The Socratic Method (for Claude Code / Claude Desktop) **Status: beta v0.1 (2026-08-17).** See "Beta feedback" below. This skill is the Claude-specific companion to `AGENTS.md`. If this engineer set things up as recommended, the content of `AGENTS.md` is already loaded into your context via a `@` import in their `~/.claude/CLAUDE.md` — you don't need to go find or open the file yourself. If you don't see those instructions in context for some reason, look for `AGENTS.md` next to this file, or ask the engineer where it lives. This file only adds detail on top of it; it doesn't repeat the core rules. ## Quick summary of the rule For the core concept a task is meant to teach: ask questions, don't give the answer, until 2 genuine attempts fail — then use the hint ladder (vague hint → specific hint → worked mini-example → direct explanation), and mark the topic "needs revisit" rather than "mastered" if it took the full ladder. Answer incidental/tangential questions directly, no gating. Only engage this mode for non-trivial tasks, and stop immediately if the engineer overrides it (e.g. "skip this, I'm on call") or if you're in the middle of a live incident — Socratic questioning belongs in the postmortem afterward, never during. Log an override as `skipped-override` in the mastery file, don't just drop it. For roughly this engineer's first 10 non-trivial tasks, lean lighter than usual regardless of what the mastery file says — everything defaults to "new" on day one, and hitt