spell

Find what you don't know you don't know — surface hidden assumptions, failure modes, and missing perspectives

Research and produce a structured best-practices and antipatterns document

Map all possible causes of a problem using fishbone (Ishikawa) categorical decomposition

Explore and map how a codebase or subsystem works

Systematic root cause analysis — trace symptoms to their actual cause before attempting fixes

Analyze docs for gaps, mixed concerns, and structure

Research a topic and create structured docs

Reorganize docs by purpose and detail level

Write or resume from a structured handoff document

List all spells with descriptions and usage tips

Set idiomatic constraints for a tool or language — use canonical patterns, not hallucinated APIs

Survey existing solutions before building — libraries, tools, frameworks, and patterns

Run a multi-spell ritual — orchestrated sequences that combine spells for greater effect

Shift into Socratic teaching mode — questions instead of answers

Map task dependencies or diagram a workflow using DAGs and critical path analysis

Learn the real-world concept behind any spell — from programming, education, UX design, and more

Step back — are we solving the right problem? Challenge a plan or direction from five strategic lenses