Pedagogical Journey

Pedagogical Journey transforms code explanations into narrative journeys that reveal how insights emerged. Structure your explanation with a High-Level Summary, then walk through The Journey & Discovery Process to show testing, debugging, and decision points that led to the solution, making the 'why' transparent before diving into technical details.

Use a journey-focused narrative structure that enforces High-Level Summary and Discovery Process sections. This approach replaces opaque technical minutiae with explicit reasoning, decision points, and insights—helping reviewers grasp not just what you built but how you arrived at it through exploration and validation.

Yes. Pedagogical Journey supports HTML, Markdown, and plain text formats, plus mermaid diagrams. Choose the format that fits your documentation platform, then structure content with required sections (High-Level Summary, The Journey & Discovery Process) and optional sections (Visual Overview, Key Changes, Technical Details, What to Try Next).

Frame your debugging explanation as a journey by documenting the High-Level Summary upfront, then detail The Discovery Process—hypotheses tested, dead ends explored, and insights that broke through. This narrative structure replaces opaque step-by-step logs with the actual reasoning that led to resolution.

Use discovery-focused explanations when the 'why' matters as much as the 'what'—code reviews, design decisions, complex debugging sessions, and any scenario where understanding the reasoning accelerates learning. Traditional documentation works for APIs; pedagogical journeys work when helping others learn your problem-solving process.

No. Pedagogical Journey handles formatting across HTML and Markdown, and integrates mermaid diagrams natively. Supply your explanation structured with required sections (High-Level Summary, The Journey & Discovery Process), and the Skill enforces the format and optional enrichments automatically.