This skill should be used when the user asks to "investigate ezCater systems", "research architectural decisions", "understand code evolution", "find historical context", "analyze project history", "search internal documentation", or needs to understand why technical decisions were made at ezCater. Use this for lighter research where the user doesn't explicitly request "deep research" (which triggers the agent).
/plugin marketplace add dhughes/claude-marketplace/plugin install ezcater-research@doug-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples/architectural-decision.mdexamples/code-evolution.mdexamples/process-understanding.mdreferences/atlassian-cli-guide.mdreferences/github-git-analysis.mdreferences/glean-search-guide.mdreferences/synthesis-reporting.mdInvestigate ezCater codebases, architectural decisions, and project histories using multiple data sources including Glean, Atlassian (Jira/Confluence), GitHub, and Git.
ezCater research requires synthesizing information from multiple internal sources. This skill provides proven methodologies for:
When to use this skill vs deep research agent:
Cannot access resources directly. Must use appropriate tools:
mcp__glean__company_search, mcp__glean__chat)atl CLI for all Jira and Confluence accessatl jira issue view FX-123, atl confluence search "keywords"gh CLI for PR/issue searches"Why was X chosen over Y?"
atl jira search "project = <PROJECT> AND text ~ 'keywords'"gh pr list --search "keywords" --repo owner/repogit log --grep="pattern"See references/glean-search-guide.md for detailed Glean querying strategies.
See examples/architectural-decision.md for a complete walkthrough.
"How did feature X evolve over time?"
git log --follow -p -- <file>gh pr list --search "feature-name"atl jira search "project = FX AND summary ~ 'feature'"See references/github-git-analysis.md for git history techniques.
See examples/code-evolution.md for a complete example.
"How do I get an order to state X?" or "What triggers workflow Y?"
atl confluence search "order process" for diagrams and specsSee references/atlassian-cli-guide.md for atl CLI patterns.
See examples/process-understanding.md for a workflow investigation example.
"How does system A interact with system B?"
atl confluence search "architecture"gh pr list --search "systemA systemB"Use Glean MCP for internal information:
Query: "order management migration decision"
Datasources: ["confluence", "slack", "gdrive"]
Effective queries:
See references/glean-search-guide.md for complete search strategies.
Search Jira tickets:
atl jira search "project = FX AND text ~ 'delivery tracking'"
atl jira issue view FX-4623
Search Confluence:
atl confluence search "order state machine"
atl confluence page view 12345678
See references/atlassian-cli-guide.md for full command reference and examples.
Search PRs:
gh pr list --repo ezcater/ez-rails --search "authentication" --limit 20
gh pr view 1234 --repo ezcater/ez-rails --json title,body,comments
Search issues:
gh issue list --repo ezcater/delivery-management-rails --search "seeder"
File evolution:
git log --follow -p -- path/to/file.rb
git blame path/to/file.rb
Commit searches:
git log --grep="feature flag"
git log --all --grep="migration"
See references/github-git-analysis.md for advanced git techniques.
After gathering information from multiple sources:
See references/synthesis-reporting.md for detailed synthesis techniques.
Structure research findings clearly:
Executive Summary: Direct answer (2-3 sentences)
Key Findings:
Historical Context (if relevant):
References:
gh pr list --search "initial [feature]" to find first PRgit log --since="1 month ago" --grep="[feature]"gh pr list --search "is:merged [feature]"atl jira search "project = FX AND text ~ 'error'"EngPortal content comes from GitHub files:
https://engportal.ezcater.com/docs/.../component/repo-name/pathhttps://github.com/ezcater/repo-name/blob/main/path.mdAccess via:
/Users/doughughes/code/ezcatergh CLI to read from GitHubIf repository exists under /Users/doughughes/code/ezcater:
ezCater has many interconnected projects:
When researching cross-project features, check all relevant repositories.
For detailed techniques and patterns, consult:
references/glean-search-guide.md - Glean search strategies and datasource selectionreferences/atlassian-cli-guide.md - Complete atl CLI command referencereferences/github-git-analysis.md - Advanced gh CLI and git history techniquesreferences/synthesis-reporting.md - Connecting dots and reporting findingsWorking examples of research investigations in examples/:
examples/architectural-decision.md - Researching why a technology was chosenexamples/code-evolution.md - Tracing feature implementation over timeexamples/process-understanding.md - Understanding workflows and state transitionsUse the deep research agent (by saying "do deep research" or "deep research needed") when:
For straightforward searches, PR lookups, or single-system investigations, this skill provides efficient guidance without the overhead of the autonomous agent.
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.