explain

Translate jig vocabulary and dense artifacts into plain language.

5|Updated May 12, 2026

Search Tags:#onboarding #artifact #lexicon #explain #plain-language #jig

Ready to run

npx skills add https://github.com/ramboz/jig --skill explain-ramboz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/ramboz/jig/tree/main/skills/explain
Command: npx skills add https://github.com/ramboz/jig --skill explain-ramboz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates jig vocabulary and dense artifacts into plain language for readers who are new to spec-driven work.

Core Features & Use Cases

Term mode: look up lexicon terms and present plain definitions with examples and see-also references.
Artifact mode: walk through specs or ADRs with inline term definitions and auto-pulled linked references.
Passage mode: explain pasted jig outputs by identifying terms and offering a plain-language interpretation.

Quick Start

Explain a single term or artifact in plain language for a junior reader.

Frequently Asked Questions about explain

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

FAQPage Schema

How do I explain jig vocabulary and dense artifacts in plain language?▼

To explain jig vocabulary in plain language, use a dedicated translation mode that looks up lexicon terms and presents definitions with examples. It translates dense artifacts into readable content for users new to spec-driven work.

Can I walk through specs and ADRs with inline lexicon definitions?▼

Yes, you can walk through specs or ADRs using artifact mode, which provides inline term definitions and automatically pulls linked references. This simplifies reading dense artifacts for junior team members.

What is the best way to understand pasted jig outputs without reading the full spec?▼

The best way to understand pasted jig outputs is using passage mode, which identifies embedded terms and offers a plain-language interpretation. This helps readers new to spec-driven work grasp complex outputs quickly.

Does this plain-language translation approach write files or modify existing code?▼

No, this plain-language translation approach does not write files or modify existing code. All outputs are strictly ephemeral, ensuring your specs, ADRs, and lexicon remain untouched during the walkthrough process.

When do I need plain-language definitions for spec-driven work?▼

You need plain-language definitions for spec-driven work when onboarding junior readers who must understand dense artifacts. It bridges the gap between complex jig vocabulary and practical comprehension without requiring prior lexicon knowledge.

Are linked references automatically loaded when explaining an artifact?▼

Yes, linked references are automatically loaded when using artifact mode to explain a spec or ADR. The loader works inline to fetch and present these references alongside the plain-language term definitions.