ezcater-research

# ezCater Research Methodology

Investigate ezCater codebases, architectural decisions, and project histories using multiple data sources including Glean, Atlassian (Jira/Confluence), GitHub, and Git.

## Overview

ezCater research requires synthesizing information from multiple internal sources. This skill provides proven methodologies for:
- Finding why architectural decisions were made
- Understanding code evolution over time
- Discovering historical context for current implementations
- Researching multi-system interactions and workflows

**When to use this skill vs deep research agent:**
- **Use this skill**: Straightforward investigations, specific PR/ticket lookups, single-source searches
- **Use deep research agent**: Complex multi-source synthesis, historical timelines, architectural decision investigations requiring extensive context

## CRITICAL: Access Requirements

**Cannot access resources directly. Must use appropriate tools:**

### Google Docs / Google Drive
- ❌ **CANNOT** access Google Docs URLs directly
- ✅ **MUST** use Glean MCP tools (`mcp__glean__company_search`, `mcp__glean__chat`)
- Glean indexes Google Docs and retrieves content

### Atlassian (Jira / Confluence)
- ❌ **CANNOT** access ezcater.atlassian.net URLs directly
- ✅ **MUST** use `atl` CLI for all Jira and Confluence access
- Commands: `atl jira issue view FX-123`, `atl confluence search "keywords"`

### GitHub
- ✅ Use `gh` CLI for PR/issue searches
- ✅ Use git commands for repository analysis
- ✅ Use Read tool for files in checked out repositories

## Research Strategy by Question Type

### Architectural Decisions

"Why was X chosen over Y?"

1. **Search Glean** for design docs, RFCs, ADRs using keywords like:
   - "[feature] decision", "[component] architecture", "why [technology]"
2. **Find epics/tickets** using `atl jira search "project = <PROJECT> AND text ~ 'keywords'"`
3. **Locate PRs** with `gh pr list --search "keywords" --repo owner/repo`
4. **Review git history** for impleme