explain

Explains project components, patterns, and decisions via the kick-off pipeline.

3|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/izantech/lineup --skill explain-izantech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain
Source: https://github.com/izantech/lineup/tree/main/.lineup-core/snapshots/skills/explain
Command: npx skills add https://github.com/izantech/lineup --skill explain-izantech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding unfamiliar codebases, architectural patterns, or past design decisions often requires digging through files manually. This Skill provides clear explanations of any project component by delegating to the Lineup kick-off pipeline's built-in explain tactic. ## Core Features & Use Cases - Component Explanation: Get a clear explanation of any project component, pattern, or decision in the codebase. - Pipeline Delegation: Runs the kick-off pipeline with the built-in explain tactic, which executes research and explanation stages automatically. - Use Case: When you encounter an unfamiliar module or wonder why a particular pattern was chosen, invoke this Skill with your question and receive a researched explanation without manual code spelunking. ## Quick Start Ask the explain skill to explain how the authentication flow works in this project.

Frequently Asked Questions about explain

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

FAQPage Schema
How do I get an explanation of a project component?

Invoke the explain skill with your question as the task description. It runs the kick-off pipeline with the built-in explain tactic, which performs research and explanation stages to answer your question.

What does the explain tactic do in Lineup?

The explain tactic is a built-in tactic resolved from the plugin's tactics directory. It executes research and explanation stages through the kick-off pipeline to clarify components, patterns, or decisions.

Does the explain skill implement its own analysis logic?

No, the explain skill is an alias that delegates entirely to the kick-off skill. It explicitly does not implement the stages itself; the kick-off pipeline resolves and executes the explain tactic.

When should I use explain instead of reading code directly?

Use explain when you need a researched, structured explanation of a component, pattern, or decision rather than raw code inspection. It is best for onboarding, architecture questions, and understanding design rationale.