project-search

# Project Search Skill

## When to use this Skill

Activate when the user:
- Asks to find or locate project content
- Uses keywords: "find", "search", "where is", "locate", "show me"
- Asks questions about project history or decisions
- Needs to find meetings, sprints, or documentation
- Wants to search by person, date, topic, or milestone
- References specific content they can't locate

## Workflow

### Phase 1: Query Analysis

**Objective**: Understand what the user is searching for and determine search strategy.

**Steps**:

1. **Parse search query** from user message:
   - Extract search terms
   - Identify search type (content, person, date, milestone, etc.)
   - Detect filters (date range, file type, status)

2. **Categorize search intent**:
   - **Content search**: "Find decisions about database"
   - **Person search**: "What has @alice worked on"
   - **Date search**: "Meetings from last week"
   - **Milestone search**: "What's in beta release milestone"
   - **Sprint search**: "Show sprint 5 stories"
   - **Topic search**: "Anything about authentication"
   - **Status search**: "Show blocked items"

3. **Extract search parameters**:
   - **Keywords**: Main search terms
   - **Person**: @mentions or names
   - **Date range**: "last week", "Q1", "after Jan 1", specific dates
   - **Content type**: meetings, sprints, docs, decisions, all
   - **Status**: completed, in-progress, blocked, planned
   - **Milestone/Sprint**: Specific milestone or sprint number

4. **Determine search scope**:
   - Project root only
   - Specific subdirectory (meetings/, sprints/, etc.)
   - Across entire workspace

**Example Analysis**:
```
User: "Find all meetings where we discussed the API design"

Parsed:
- Intent: Content search
- Keywords: ["API design"]
- Content type: meetings
- Date range: all time
- Search scope: meetings/

Strategy: README index → Content search in meetings/
```

### Phase 2: Strategy Selection

**Objective**: Choose optimal search strategy based on query