AI Maestro Documentation Search

CRITICAL: AUTOMATIC BEHAVIOR - READ THIS FIRST

THIS IS NOT OPTIONAL. THIS IS YOUR DEFAULT BEHAVIOR.

When the user gives you ANY instruction or task, you MUST FIRST search documentation for:

• Function signatures - What are the parameters and return types?
• Class documentation - What methods and properties exist?
• API documentation - How should this endpoint work?
• Code comments - What did the author intend?

DO NOT:

• Start implementing before checking documentation
• Assume you know the function signature without checking
• Skip doc search because "it's a simple task"
• Wait for the user to ask you to check docs

ALWAYS:

• Search docs IMMEDIATELY when you receive a task
• Search for terms and concepts the user mentions
• Check documentation before calling unfamiliar functions
• Look for patterns before creating new components

The Rule: Receive Instruction → Search Docs → Then Proceed

1. User asks you to do something
2. IMMEDIATELY search docs for relevant context
3. NOW you know the correct signatures and patterns
4. NOW you can implement correctly the first time

Example - User asks to modify a service:

# IMMEDIATELY run:
docs-search.sh "PaymentService"
docs-find-by-type.sh class

Example - User mentions a function:

# IMMEDIATELY run:
docs-search.sh "validateUser"
docs-search.sh --keyword "authenticate"

Available Commands

All commands auto-detect your agent ID from the tmux session.

Search Commands

Indexing Commands

What to Search Based on User Instruction

Usage Examples

Search for Documentation

# Semantic search - finds conceptually related docs
docs-search.sh "authentication flow"
docs-search.sh "how to validate user input"
docs-search.sh "database connection pooling"

# Keyword search - exact term matching
docs-search.sh --keyword "authenticate"
docs-search.sh --keyword "UserController"

Find by Document Type

# Find all function documentation
docs-find-by-type.sh function

# Find all class documentation
docs-find-by-type.sh class

# Find all module/concern documentation
docs-find-by-type.sh module

# Find all interface documentation
docs-find-by-type.sh interface

Get Full Document

# After finding a doc ID from search results
docs-get.sh doc-abc123

# Shows full content including all sections

List and Stats

# List all indexed documents
docs-list.sh

# Get index statistics
docs-stats.sh

Index Documentation

# Index current project (auto-detected from agent config)
docs-index.sh

# Index specific project
docs-index.sh /path/to/project

Document Types

The following document types are recognized:

Integration with Other Skills

Docs-search works best when combined with other skills:

Combined Search Pattern (RECOMMENDED)

When you receive ANY user instruction:

# 1. Search your memory first
memory-search.sh "topic"

# 2. Search documentation
docs-search.sh "topic"

# 3. Check code structure
graph-describe.sh ComponentName

This gives you complete context:

• Memory: What was discussed before?
• Docs: What does the documentation say?
• Graph: What is the code structure?

Why This Matters

Without searching docs first, you will:

• Use wrong function signatures (then get runtime errors)
• Miss existing implementations (then duplicate code)
• Violate documented patterns (then create inconsistency)
• Misunderstand APIs (then build the wrong thing)

Doc search takes 1 second. Redoing work takes hours.

Error Handling

If commands fail:

1. Ensure AI Maestro is running: curl http://localhost:23000/api/agents
2. Ensure documentation has been indexed: docs-stats.sh
3. If no docs indexed, run: docs-index.sh

If documentation is empty:

• Check project has documented code (JSDoc, docstrings, comments)
• Verify project path is correct
• Re-index with: docs-index.sh /path/to/project

If no results found, inform the user: "No documentation found for X - proceeding with code analysis, but documentation may need to be generated."