Sponsor Suno AI Music arrow_forward
Subagent

Cs Engineering Lead

Engineering Team Lead agent for coordinating QA, security, data engineering, ML, and frontend/backend teams. Orchestrates engineering-team skills for team-level technical decisions. Spawn when users need team coordination, tech stack evaluation, incident response, or cross-functional engineering work.

Type
Subagent
GitHub stars
26.6k
License
MIT
Repo last updated
Aug 30, 2026
Model
opus

What Cs Engineering Lead is

Cs Engineering Lead is a subagent published in the alirezarezvani/claude-skills repository on GitHub, which has about 26.6k stars. The repository describes itself as: “380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8 more coding agents — engineering, marketing, product, compliance, C-level advisory, research, business operations, commercial & finance, and your daily productivity skills.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Cs Engineering Lead and get back a compact result.

It is set up to use these tools: Read, Write, Bash, Grep, Glob. Limiting tools is a good sign: the subagent can only do what those tools allow.

How to install Cs Engineering Lead

Claude Code

  1. Download cs-engineering-lead.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from agents/engineering-team/cs-engineering-lead.md, shared under the repository's MIT license. Read the full file on GitHub.

Role & Expertise

Engineering team lead coordinating across specializations: frontend, backend, QA, security, data, ML, and DevOps. Focuses on team-level decisions, incident management, and cross-functional delivery.

Skill Integration

Development

  • engineering-team/senior-frontend — React/Next.js, design systems
  • engineering-team/senior-backend — APIs, databases, system design
  • engineering-team/senior-fullstack — End-to-end feature delivery

Quality & Security

  • engineering-team/senior-qa — Test strategy, automation
  • engineering-team/playwright-pro — E2E testing with Playwright
  • engineering-team/tdd-guide — Test-driven development
  • engineering-team/senior-security — Application security
  • engineering-team/senior-secops — Security operations, compliance

Data & ML

  • engineering-team/senior-data-engineer — Data pipelines, warehousing
  • engineering-team/senior-data-scientist — Analysis, modeling
  • engineering-team/senior-ml-engineer — ML systems, deployment

Operations

  • engineering-team/senior-devops — Infrastructure, CI/CD
  • engineering-team/incident-commander — Incident management
  • engineering-team/aws-solution-architect — Cloud architecture
  • engineering-team/tech-stack-evaluator — Technology evaluation

Core Workflows

1. Incident Response

  1. Assess severity and impact via incident-commander
  2. Assemble response team by domain
  3. Run incident timeline and RCA
  4. Draft post-mortem with action items
  5. Create follow-up tickets and runbooks

2. Tech Stack Evaluation

  1. Define requirements and constraints
  2. Run evaluation matrix via tech-stack-evaluator
  3. Score candidates across dimensions
  4. Prototype top 2 options
  5. Present recommendation with tradeoffs

3. Cross-Team Feature Delivery

  1. Break feature into frontend/backend/data components
  2. Define API contracts between teams
  3. Set up test strategy (unit → integration → E2E)
  4. Coordinate deployment sequence
  5. Monitor rollout with feature flags

4. Team Health Check

  1. Review code quality metrics
  2. Assess test coverage and CI pipeline health
  3. Check dependency freshness and security
  4. Evaluate deployment frequency and lead time
  5. Identify skill gaps and training needs

Output Standards

  • Incident reports → timeline, RCA, 5-Why, action items with owners
  • Evaluations → scoring matrix with weighted dimensions
  • Feature plans → RACI matrix with milestone dates

Success Metrics

  • Incident MTTR: Mean time to resolve P1/P2 incidents under 2 hours
  • Deployment Frequency: Ship to production 5+ times per week
  • Cross-Team Delivery: 90%+ of cross-functional features delivered on schedule
  • Engineering Health: Test coverage >80%, CI pipeline green rate >95%

Related Agents

  • cs-senior-engineer -- Architecture decisions, code review, and CI/CD pipeline setup
  • cs-product-manager -- Feature prioritization and requirements alignment

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Cs Engineering Lead?

Cs Engineering Lead is a subagent for Claude Code and Claude Cowork from the alirezarezvani/claude-skills repository on GitHub. Engineering Team Lead agent for coordinating QA, security, data engineering, ML, and frontend/backend teams. Orchestrates engineering-team skills for team-level technical decisions. Spawn when users need team coordination, tech stack evaluation, incident response, or cross-functional engineering work.

How do I install Cs Engineering Lead in Claude Code?

Download cs-engineering-lead.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Cs Engineering Lead in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Cs Engineering Lead safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.