CtrlK
BlogDocsLog inGet started
Tessl Logo

team-lead-reference

Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, and defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting a delegation session, running a multi-agent workflow, delegating work, choosing which model to use, or assigning tasks.

100

Quality

100%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Team Lead Reference

Delegation Sequence

  1. Score task complexity (table below) → determines tier
  2. Route to model tier via Cost-Aware Routing
  3. Deepen plan if 3+ subtasks (Deepen-Plan Protocol)
  4. Check pre-delegation policy (5-point checklist below)
  5. Delegate using Compact Delegation Envelope
  6. Handle output per Status Handling table
  7. Log via observability-logging skill

For the specialist agent registry and model assignments, see agent-registry.md.

Cost-Aware Model Routing

TierUse For
PremiumTeam Lead orchestration, highest-stakes decisions
QualityFeature implementation, UI/frontend, security, architecture, complex reasoning
StandardLarge-scale analysis, schema design, cost-efficient coding, repo exploration
FastTerminal-heavy tasks, E2E tests, data pipelines, agentic workflows
EconomyDocs, simple config, formatting, boilerplate

Selection: Default to agent's assigned tier. Downgrade pure docs/config → Economy. Upgrade security/architecture ambiguity → Quality/Premium. Never Premium/Quality for boilerplate. 3+ parallel agents → prefer Economy/Fast/Standard.

Complexity-Based Task Scoring

FactorLow → High
Files touched1–2 → 3–5 → 6+ / cross-library
Reasoning depthBoilerplate → pattern matching → architecture/security/tradeoffs
AmbiguityClear spec → some judgment → multiple valid approaches
RiskReversible → moderate impact → DB/auth/breaking
DependenciesNone → 1–2 upstream → complex chain
ScoreTierExamples
1–2Economy/FastDocs update, config tweak, rename, simple test
3–5Standard/QualityComponent, CMS query, API route, migration
8QualityArchitecture decision, security audit, complex refactor
13Quality + PanelDB migration with data transform, auth flow redesign

Overrides: Blocker (blocking 2+ downstream) → upgrade one tier. Security-touching → Quality+. Pure docs → Economy. Registry default takes precedence unless complexity clearly warrants change.

Deepen-Plan Protocol

Plan ComplexityAction
1–2 subtasks, familiarSkip — delegate directly
3–5 subtasks, mixedQuick deepen — single Researcher sub-agent
6+ subtasks, unfamiliarFull deepen — parallel Researcher sub-agents

Quick deepen: Fire one Researcher for exact file paths & line numbers, patterns to follow (file:line examples), relevant lessons from LESSONS-LEARNED.md, and risks/blockers per subtask. Full deepen: Split by domain into parallel Researchers. See agent-registry.md for scope examples.

FieldBefore DeepenAfter Deepen
Files"some component"Exact path + line range
Pattern"follow existing style"Specific file:line reference
RisksunknownKnown issues identified
LessonsuncheckedRelevant lessons applied
DependenciesassumedVerified with exact imports

Agent Output Status Handling

StatusAction
CompleteFast review
Complete with concernsResolve before review
Needs contextProvide info; re-dispatch
BlockedUpgrade model/escalate; never re-dispatch unchanged

Pre-Delegation Policy Checks

  1. Tracker issue exists for this task
  2. File partition is clean (no overlap with parallel agents)
  3. All dependency tasks are Done
  4. Delegation prompt has file paths + acceptance criteria
  5. Self-improvement reminder included (Read LESSONS-LEARNED.md first)

Feature work adds: (6) Known issues reviewed, (7) Architecture docs read, (8) Existing code searched. High-risk work adds: (9) Panel review planned, (10) Rollback path identified.

Compact Delegation Envelope

{
  "tracker": "TAS-XX",
  "agent": "Agent Name",
  "objective": "One sentence: what to do and why.",
  "files": ["path/to/file.ts", "path/to/other.ts"],
  "acceptance_criteria": ["AC 1", "AC 2"],
  "constraints": "Only modify listed files. Read LESSONS-LEARNED.md first.",
  "output_contract": "Return: files changed, lint/type/test pass/fail, discovered issues."
}

tracker required; acceptance_criteria verbatim from tracker; files = exact resolved paths (not globs); output_contract = agent's Base Output Contract. Maintain running delegation log in session checkpoint (see session-checkpoints skill).

Context Source Tagging

Prefix each agent's output summary ### [Agent Name] TAS-XX Description. Never merge outputs from different agents. Cite source agent when referencing prior output. Include Agent column in checkpoint "Completed Work" tables.

Dead Letter Queue Format

Log to .opencastle/AGENT-FAILURES.md when agent fails 2+ attempts, background output fails all gates, or unrecoverable error occurs. Panel 3x BLOCK → create dispute instead.

Entry (DLQ-XXX: Short description): Date, Agent, Tracker Issue, Failure Type (verification-fail / tool-error / panel-block / timeout / scope-creep), Attempts, Task, Failure Details, Resolution. Scan DLQ for pending retries at session start.

Error Recovery

For common failure modes and recovery procedures, load the orchestration-protocols skill.

Dispute Protocol

Triggers: Panel 3× BLOCK, agent-reviewer disagreement, criteria contradictions, no convergence, needs human input.

Create in .opencastle/DISPUTES.md:

  1. Number (DSP-XXX), set priority, document both perspectives with file references
  2. Build attempt history; present ≥2 options with rationale/risk
  3. Link panel reports, DLQ entries, changed files
  4. Log with observability-logging dispute command

After resolution: resolved → re-delegate with decision as constraint. deferred → follow-up issue.

Repository
monkilabs/opencastle
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.