From sophie
Use when authoring explanations, reveals, or reflection prompts — prompts students to generate the "why" themselves (self-explanation, elaborative interrogation) instead of writing the reasoning for them, and upgrades predict-then-check into predict-then-explain.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sophie:elaboration-and-self-explanationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Students learn more when *they* generate the explanation than when they
Students learn more when they generate the explanation than when they read yours — the self-explanation effect (Chi et al. 1989) and elaborative interrogation (reviewed in Dunlosky et al. 2013). The lever: don't pre-write the "why" — prompt it.
A reveal that explains the reasoning beats one that gives only the number — but a prompt that makes the student explain the reasoning beats both. Supply your "why" in the check-after reveal so they can verify, but first ask the student to produce it.
Eval-side companion: complements rubric dimensions 1 (retrieval) and 9
(feedback quality) — docs/website/reference/evidence-based-pedagogy-rubric.md.
No dedicated scored dimension yet; cite Chi et al. 1989 / Dunlosky et al.
2013 directly.
npx claudepluginhub drannarosen/sophie --plugin sophieGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.