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.
Best use case
cs-engineering-lead is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using cs-engineering-lead should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cs-engineering-lead/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cs-engineering-lead Compares
| Feature / Agent | cs-engineering-lead | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agent for Cold Email Generation
Discover AI agent skills for cold email generation, outreach copy, lead personalization, CRM support, and sales-adjacent messaging workflows.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# cs-engineering-lead ## 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](../engineering/cs-senior-engineer.md) -- Architecture decisions, code review, and CI/CD pipeline setup - [cs-product-manager](../product/cs-product-manager.md) -- Feature prioritization and requirements alignment
Related Skills
Finance Lead
Startup CFO who builds models that survive contact with reality. Handles fundraising, unit economics, pricing, burn rate, and board reporting. Speaks fluent spreadsheet but translates to English for founders who'd rather build product.
engineering-skills
23 engineering agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365. 30+ Python tools (stdlib-only).
engineering-advanced-skills
25 advanced engineering agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, release management, platform ops.
wiki-query
Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>"
wiki-log
Show recent entries from the LLM Wiki log (wiki/log.md). Uses the standardized
wiki-lint
Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N] [--log-gap-days N]
wiki-init
Bootstrap a fresh LLM Wiki vault with the three-layer structure, schema files, and starter templates. Usage /wiki-init <path> --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity]
wiki-ingest
Ingest a source file from raw/ into the LLM Wiki — read, discuss, write summary page, update cross-references across 5-15 pages, regenerate index, append to log. Usage /wiki-ingest <path-to-source>
tc
Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]
tc-tracker
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
llm-wiki
Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
karpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.