Skill: Eliminate/Automate/Delegate Triage

Capability Domain: Process Engineering
Technology Stack: AWS Lambda, Guardrails, LLM Agents

Recipe

1. Work the Action Register (one row per constraint from the Cost of Delay Ranking) in impact order — don't fill "automate" before answering "can this step be removed" in writing.
2. Eliminate if the step is stale policy, a duplicate check, or pure handoff queue with no work.
3. Automate if mechanical and safe to retry. Default: one Lambda plus one Guardrail.
4. Delegate only if judgment remains that a Guardrail cannot encode. Write the agent's scope in the same row. Do not invent an agent catalog from the AI matrix.
5. The AI Opportunity Prioritization Matrix may mark where automate/delegate could apply. It never skips eliminate.
6. On the same row, tag cause layers and a route. A constraint may carry more than one tag (environment and knowledge and individual). Classification is not disposal — keep every applicable tag.

Cause tags

• dE (environment): tool, data, process, incentive, time, or authority. Default owner is process/tooling — not a course.
• dK (knowledge/skill): people do not know or cannot yet do the work. Trainable or selectable; not a Lambda.
• dI (individual): selection, capacity, or motivation. Not a lesson and not a bot.

"People doing it wrong" is not automatically dK. If they know the right move and the environment punishes it, that slice is still dE. If they will not or cannot, that slice is dI.

Routes (receiving playbook / owner)

Write one route per tag on the row. Do not invent a second register.

Tag + decision	Route
dE + eliminate	Drop the step. No receiving playbook.
dE + process/tooling change (policy, required check, incentive, buy/configure a tool)	Process/tooling owners. Not AI SDLC by default.
dE + automate or delegate (step must stay; encode or hand to an agent)	AI SDLC candidate only.
dK	Team Upskill Engine input: ranked, evidenced gap candidates (stage, clock, unit, n, role). TUE still builds Areas of Performance, master-performer patterns, and evidence scoring. This playbook does not author modules.
dI	Staffing / selection. Out of both AI SDLC and Team Upskill Engine curriculum.

Row contract

Each Action Register row records: finding, eliminate/automate/delegate decision + rationale, cause tags (multi), route per tag, and the evidence pointer (clock, unit, sample size).

Escalate

• 1 impact constraint where eliminate and automate are both ruled out — flow redesign, not a tool.

Pitfalls

• Reaching for automation or an agent before ruling out elimination.
• Treating the AI matrix as an implementation backlog.
• Mapping every dE row to AI SDLC.
• Authoring Team Upskill Engine modules or a Roles & Performance Map here.
• Forcing a single cause tag on a mixed bottleneck.