delegation

Assign Team Rep and Epic Ownership roles to distribute engineering management workload.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill delegation-imsus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegation
Source: https://github.com/imsus/cto/tree/main/.agents/skills/delegation
Command: npx skills add https://github.com/imsus/cto --skill delegation-imsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Delegation helps engineering managers stop being the bottleneck by moving day-to-day operational load and new project ownership off their plate, while still preserving quality and standards.

Core Features & Use Cases

  • Team Rep for operations: Rotates responsibility for alerts, support requests, debugging, and incident coordination so the manager is no longer the first call.
  • Epic Ownership for new projects: Assigns an engineer as the owner who meets the PM, writes the technical design, breaks down tasks, and makes key decisions.
  • Ownership patterns that prevent the “go-to person” trap: Establishes kingdom ownership and decision rights so questions route to the correct owner instead of everything flowing back to the manager.

Use case scenarios: You’re saying “I can’t let go,” engineers don’t take initiative, you’re getting pulled into every decision, the team lacks bus-factor coverage, or you feel like you work weekends to keep things moving.

Quick Start

Use delegation when you need to reduce your bottleneck by assigning one person to run daily operational coverage and a separate person to own each new epic end-to-end.

Frequently Asked Questions about delegation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop being the engineering bottleneck for every operational decision?

To stop being the engineering bottleneck, delegate operational load using a Team Rep pattern to route alerts and incidents, and assign Epic Ownership for new projects so engineers handle technical designs and decisions directly.

What is the best way to assign project ownership without micromanaging the team?

Assign project ownership without micromanaging by establishing decision rights and kingdom ownership, matching delegation depth to task-relevant maturity, and letting the designated Epic Owner manage task breakdowns and PM communication.

How do I reduce bus-factor risk in my engineering team?

Reduce bus-factor risk by rotating operational responsibilities through a Team Rep system and distributing new project ownership across different engineers to ensure critical knowledge and decision-making are shared.

How do I get engineers to take initiative and stop escalating decisions to management?

Get engineers to take initiative by implementing a structured delegation contract that defines ownership boundaries, routes questions to the correct Epic Owner, and empowers engineers to make key technical decisions without manager approval.

When should I use a Team Rep versus an Epic Owner for delegation?

Use a Team Rep to rotate daily operational coverage like alerts and debugging, and use an Epic Owner to lead a new project end-to-end from technical design to task breakdown, ensuring neither role overloads a single engineer.