explain

Explain code and architecture with structured, audience-appropriate templates.

4|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/finger-gun/sisu --skill explain-finger-gun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/finger-gun/sisu/tree/main/packages/skills/skill-explain
Command: npx skills add https://github.com/finger-gun/sisu --skill explain-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clears up complex code and architecture for diverse audiences by providing structured, readable explanations that map modules, data flows, and entry points.

Core Features & Use Cases

  • Structured, template-based explanations for code, APIs, and design decisions.
  • Onboarding and code-review aids by translating technical details into approachable narratives.
  • Use Case: A developer needs to explain a new module to non-technical stakeholders.

Quick Start

Provide a module name and its responsibilities to generate a clear, audience-appropriate explanation.

Frequently Asked Questions about explain

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

FAQPage Schema
How do I explain code architecture to non-technical stakeholders?

To explain code architecture to non-technical stakeholders, provide a module name and its responsibilities to generate a structured, approachable narrative. This translates complex technical details into readable explanations tailored for diverse audiences.

What is the best way to document software modules for onboarding?

The best way to document software modules for onboarding is using a reusable template that maps modules, data flows, and entry points. This produces concise, structured explanations that help new team members quickly understand the architecture.

Can I use a template to explain APIs and design decisions?

Yes, you can use a template to explain APIs and design decisions. The template enforces a structured workflow that produces readable explanations, mapping technical details into approachable narratives suitable for code reviews and design discussions.

How do I generate concise explanations for code reviews?

To generate concise explanations for code reviews, apply a structured explanation workflow with a defined template. This translates technical implementation details into clear, audience-appropriate narratives, ensuring reviewers quickly grasp the architecture and data flows.

Does this approach work for varying levels of architectural detail?

Yes, this approach works for varying levels of architectural detail. It produces structured explanations across software modules, APIs, and architectural diagrams, allowing you to adjust the depth of technical details based on the specific audience and discussion context.