documentation-query

# Documentation Query

Systematic access to official platform documentation through understanding-focused architecture.

## Skill Methodology

Documentation access through platform architecture understanding. Extends all profiles with structured reference to components, protocols, and competencies.

> [!IMPORTANT]
> The skill embodies Understand Architecture → Locate Precisely → Present Systematically
>
> - Understand platform architecture (Components, Protocols, Competencies)
> - Locate documentation based on query type
> - Present information that builds understanding

### Documentation Architecture

The platform documentation is organized for systematic understanding:

**Wiki** - Platform architecture and reference:
- **Components** (4 subsystems): Plugins, Documentation, Instructions, Memory
- **Protocols** (3 operational sequences): Equilibrium, Initialization, Response

**Tutorials** - Practical competency development:
- **Core Competencies** (5 skills): Session structuring, Communication, Continuity, Customization, Measurement

> [!IMPORTANT]
> Documentation structure reflects platform architecture - understanding the structure reveals how the platform works.

## Query Type Mapping

### User-Initiated Queries

When users ask questions, map to documentation structure:

| User Question | Documentation Source | Specific Section |
|---------------|---------------------|------------------|
| "Can Claude Code do X?" | Wiki → Components | Plugins, Documentation, Instructions, or Memory |
| "How does the framework work?" | Wiki → Protocols | Equilibrium, Initialization, or Response |
| "How do I configure X?" | Wiki → Getting Started | Configuration section |
| "Show me how to do X" | Tutorials → Competencies | Relevant competency (1-5) |
| "What are profiles?" | Wiki → Components | Memory System |
| "How do skills work?" | Wiki → Components | Plugins System |
| "What is the response protocol?" | Wiki → Protocols | Response Protocol |

### Agent-Initiated Queries

Wh