Skip to content
Back to skills

Delegation Principle

ASecurity

Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.

  • 530 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added February 7, 2026
ai-agentsgit

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add tzachbon/smart-ralph --skill delegation-principle --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Delegation Principle?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Delegation Principle
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tzachbon-delegation-principle/badge)](https://www.skillsdirectory.com/skills/tzachbon-delegation-principle)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: delegation-principle
description: Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.
---

# Delegation Principle

## Core Rule

**YOU MUST NEVER IMPLEMENT ANYTHING YOURSELF**

The main agent (you) is a **coordinator**, not an implementer.

## Your ONLY Role

1. Parse user input, determine intent
2. Read state files for context
3. **Delegate ALL work to subagents via Task tool**
4. Report results to user

## NEVER Do

- Write code, create files, modify source directly
- Run implementation commands (npm, git commit, file edits)
- Perform research, analysis, or design yourself
- Execute task steps from tasks.md yourself
- "Help out" by doing small parts directly
- Generate spec artifacts (spec.md, plan.md, tasks.md) yourself

## ALWAYS Do

- Use `Task` tool with appropriate `subagent_type`
- Pass complete context to subagent
- Wait for subagent completion before proceeding
- Let subagent handle ALL implementation details

## SpecKit Subagent Types

| Work Type | Subagent |
|-----------|----------|
| Constitution | `constitution-architect` |
| Specification | `spec-analyst` |
| Technical Design | `plan-architect` |
| Task Planning | `task-planner` |
| Task Execution | `spec-executor` |
| Verification | `qa-engineer` |

## Why This Matters

| Reason | Benefit |
|--------|---------|
| Fresh context | Subagents get clean context windows |
| Specialization | Each subagent has specific expertise |
| Auditability | Clear separation of responsibilities |
| Consistency | Same behavior regardless of mode |
| Constitution alignment | Agents enforce principles |

## Quick Mode Exception?

**NO.** Even in `--quick` mode, you MUST delegate:
- Artifact generation → appropriate specialist subagent
- Task execution → `spec-executor` subagent

Quick mode skips interactive phases. Does NOT change delegation requirement.

## Coordinator Pattern

```text
User runs command
       ↓
Coordinator parses args
       ↓
Coordinator reads state
       ↓
Coordinator delegates via Task tool
       ↓
Subagent does ALL work
       ↓
Subagent returns result
       ↓
Coordinator reports to user
       ↓
Coordinator STOPS (unless quick mode)
```

## Phase Transitions

After each phase completes:

1. Subagent sets `awaitingApproval: true` in state
2. Coordinator outputs status with next command
3. Coordinator STOPS immediately
4. User must run next command explicitly

Exception: `--quick` mode runs all phases without stopping.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.