Engineering Task Routing and Handoff
Choose the right engineering specialist, resolve ambiguous ownership, and produce a focused handoff with clear acceptance checks.
Before & after
Same prompt, same agent — the only difference is the skill.
There are lots of engineering resources available depending on what your team needs. You might want to look into different frameworks and tools. Various platforms offer guides and documentation. The specific skills your team needs depend on your tech stack and the problems you're trying to solve. There are probably some good communities and learning resources out there. I'd be happy to help you think through what areas might be important for your team to develop.
ENGINEERING SKILLS INDEX (public GitHub: alirezarezvani/claude-skills) Available role skills: 337 total Fold into: Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools ARCHITECTURE TRACK: CTO Review (scaling, tech debt, rebuild vs vendor) SRE Engineer (SLOs, error budgets, incident response) Backend Development (API design, async patterns) SECURITY TRACK: Security Review (threat model, vulnerability scanning) Infra Security (secrets management, network isolation) QA & TESTING: Playwright Pro (end-to-end testing) DATA ENGINEERING: BigQuery Schema Design Data Pipeline Audits FREQUENT COMBOS: Architecture question? Load cto-review SKILL.md Building payment flow? Load stripe skill + backend skill Infra problem? Load sre-engineer + your-cloud-provider skill INSTALL PATTERN: Never bulk-load the bundle. Cherry-pick only the SKILL.md you need per task.
About this skill
“Is this a backend issue, an infrastructure issue, or something QA should investigate?” Tool names and visible symptoms often point to the wrong owner. This skill selects one entry-point specialist, explains the evidence behind that choice, and preserves the context needed to start useful work.
What it does
- Distinguishes architecture, frontend, backend, QA, DevOps, security, AI/ML, and data engineering work by the decision or artifact required.
- Separates observed symptoms from suspected causes so “it runs on AWS” does not automatically become an infrastructure assignment.
- Resolves cross-discipline requests by identifying the first blocking dependency and a specific condition for involving another specialist.
- Turns vague requests into provisional routing decisions with a bounded first diagnostic step.
- Produces handoffs containing known facts, unknowns, scope boundaries, and observable acceptance checks.
- Selects from an available specialist catalog without assuming additional skills are installed or loading an entire bundle.
What you get
A concise routing decision for a quick question, or a ready-to-use specialist handoff for a larger task. Ambiguous cases include the evidence needed to confirm or change the assignment.
Best for
Developers and engineering leads assigning unfamiliar work, resolving ownership disputes, or choosing among specialist skills without filling the session with unrelated instructions.
SKILL.md preview
---
name: engineering-task-routing-and-handoff
description: Routes engineering requests to one entry-point specialist by separating symptoms from causes, ranking the plausible causes from the symptom pattern, identifying the first blocking dependency, and writing an evidence-preserving handoff with concrete diagnostics and acceptance checks. Use when the user says "which engineering specialist should handle this", "is this backend or DevOps", "pick the right skill for this task", "this ticket keeps bouncing between teams", "my app keeps failing and nobody owns it", "turn this request into a specialist handoff", or "do we need architecture or implementation help".
---
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.