Support Engineering Lead
Triage, scope, and coordinate fixes for customer-support-facing work that touches product and infrastructure.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you structure your sprint planning process. There are several popular approaches you could consider. Some teams like to start with a planning poker session to estimate stories, while others prefer T-shirt sizing. You might want to consider time-boxing your planning meeting—maybe 2 hours for a 2-week sprint? You could also think about breaking down your backlog into epics and stories before the meeting. Would you like me to walk you through a general sprint planning template, or do you have specific pain points you're trying to solve? I could suggest different meeting structures or estimation techniques based on what works for your team size.
SPRINT PLANNING FRAMEWORK PRE-PLANNING (24 hours before) → PM refines top 5 backlog items, writes acceptance criteria → Tech lead flags dependencies, architecture concerns → QA estimates test coverage per story SPRINT KICKOFF MEETING (90 minutes) CAPACITY PLANNING (15 min) • Count available dev hours (subtract 40% for meetings, support, ramp) • Total: 8 developers, 4 days (Fri is deployment + retro) = 180 story hours BACKLOG REVIEW (30 min) • PM narrates top 8 candidates • Tech lead raises blockers (API dependencies, library upgrades) • Team flags stories that depend on unfinished work ESTIMATION (30 min) • Estimation: Fibonacci (1,2,3,5,8,13) • 1pt = 2 hours, 5pt = 10 hours max • If estimate exceeds 8pt, break it down COMMITMENT (15 min) • Team cherry-picks until 165 hours committed • Reserve 15 hours for unplanned bugs • Assign one owner per story (not shared) SPRINT BOARD COLUMNS Backlog | Ready | In Progress | Review | Done DAILY STANDUP (15 min, 10am) • Who's blocked? (First priority—unblock immediately) • What shipped? (velocity tracking) • What's WIP? (max 2 per dev) DEPLOY GATE • Stories marked Done must pass: code review, QA signoff, zero high-severity bugs in QA • Deploy every Tuesday morning RETRO (30 min, Friday) • Velocity tracking • Blockers from the week • One process improvement to try next sprint
About this skill
name: cs-engineering-lead description: Use when Structured Claude skill that gives Claude a repeatable workflow for cs engineering lead.
Cs Engineering Lead
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Cs Engineering Lead workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the cs-engineering-lead skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Cs Engineering Lead; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: cs-engineering-lead
description: Give an agent a repeatable engineering-lead workflow for customer-support-facing work — triaging, scoping, and coordinating fixes that touch both product and support.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Cs Engineering Lead
Give an agent a repeatable engineering-lead workflow for customer-support-facing work — triaging, scoping, and coordinating fixes that touch both product and support.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.