Lead Agent — Development agent for Claude Code
The orchestrator ROLE for non-trivial multi-discipline work.
How to install Lead Agent
Installs to ~/.claude/agents/raiharsh1992-crew-for-claude-lead-agent.md
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/raiharsh1992/crew-for-claude/HEAD/.claude/agents/lead-agent.md -o ~/.claude/agents/raiharsh1992-crew-for-claude-lead-agent.md Restart Claude Code, or start a new session, for it to be picked up.
What Lead Agent does
name: lead-agent description: The orchestrator ROLE for non-trivial multi-discipline work. The MAIN SESSION (the user-facing Claude) performs this role directly — lead-agent is NOT spawned as a sub-agent. This file documents the role's responsibilities. Decompose the request, route each piece to the appropriate domain lead, integrate results, report back to the user. tools: Read, Grep, Glob, Write, Edit, Bash, Task, Workflow, WebFetch, TodoWrite model: opus
**READ THIS FIRST — lead-ag
Alternatives in Development
- Svelte Recurrence Sweep — Given a defect just found or fixed in a SvelteKit app (apps/moderator, apps/auth, apps/creator-studio), finds 7.2k ★
- Code Reviewer Pro — Role: Senior Staff Software Engineer specializing in comprehensive code reviews for quality, sec 1.5k ★
- Learning Reviewer — Internal agent for reviewing learnings and promoting them to rules or skills 150 ★
Full documentation available on GitHub
View Source RepositoryRelated Agents
Main
Mercury orchestrator role definition. NOT meant to be spawned as a sub-agent — this file documents the behavio
Org Reviewer
First-pass code review against the organization rubric before a change goes to main. Read-only; reports findin
Feature Estimator Summary
Sub-agent of the feature-estimator pipeline. Writes the client-facing Dutch executive summary (samenvatting).
Context Pack Loader
Loads a mode-scoped context pack instead of the full agent-facing reference docs. Operator invokes via "load c
Salesforce Repository Analyst
Read-only agent that maps the full impacted execution path (trigger/handler/service/selector/LWC/Flow) for a r
Tp Commit Writer
PROACTIVELY use this when the user is about to commit a NON-TRIVIAL change (new feature, fix, refactor) and as
Related Skills
Aegis Return Format
Sub-agent return format — every non-trivial claim must be tagged [VERIFIED: ] (backed by executed command) or
Model Provider
Switch the default model provider for sf's spawned build/test sub-agents: anthropic (default), codex, or curso
Blueprint
You MUST use this for ANY non-trivial implementation task. Skipping planning leads to confident mistakes that