explain

Trace call flows and explain code areas for developer understanding.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CuongTran69/tramthientra --skill explain-cuongtran69
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/CuongTran69/tramthientra/tree/main/.augment/skills/explain
Command: npx skills add https://github.com/CuongTran69/tramthientra --skill explain-cuongtran69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers, reviewers, and onboarders move from surface-level reading to true understanding by turning opaque code and feature areas into clear mental models. It prevents shallow explanations and reduces knowledge gaps that cause repeated questions, buggy changes, and slow onboarding.

Core Features & Use Cases

  • Feynman Loop Workflow: Iterative explore → explain → find gaps → re-explore to converge on clear, testable explanations.
  • Codetrace & Mapping: Trace entry points, call flows, dependencies, and side effects across files to reveal design intent and risks.
  • Practical Use Cases: Onboard new team members to a service, prepare a design doc by extracting rationale from code, or explain a failing feature during debugging.

Quick Start

Ask the assistant to explain how the authentication feature works by tracing entry points, data flow, and key design decisions.

Frequently Asked Questions about explain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I understand a complex codebase for developer onboarding?

To understand a complex codebase for developer onboarding, you can trace entry points, call flows, and dependencies to build a clear mental model. This process uses iterative code retrieval and progressive simplification to surface design rationale and reveal knowledge gaps.

What is the Feynman Loop technique for code comprehension?

The Feynman Loop for code comprehension is an iterative workflow: explore the code, explain it, find gaps in the explanation, and re-explore to converge on a clear, testable mental model. It prevents shallow reading by forcing progressive simplification.

How do I trace call flows and side effects when debugging a feature?

To trace call flows and side effects when debugging, perform iterative code retrieval and grep operations across files. This maps dependencies and traces entry points to reveal design intent and potential risks within the failing feature flow.

Can I extract design rationale from existing code to prepare a design doc?

Yes, you can extract design rationale from existing code to prepare a design doc by applying an iterative exploration loop. This process traces data flow and maps dependencies to surface the original design intent hidden within opaque feature areas.

What is the best way to explain a feature flow to a new developer?

The best way to explain a feature flow to a new developer is using an iterative explore-and-explain loop. This method traces entry points and simplifies complex code progressively, turning opaque feature areas into clear, testable mental models.