worker-architect

Design workers that make delegation cleaner, not busier.

This skill owns roster design for AI workers and delegated systems: what jobs deserve a stable worker, what should stay as a skill on an existing worker, where boundaries belong, what loadout is justified, and how handoffs should work. Use it when the system needs sharper ownership instead of more role theater.

Scope

Use this skill for:

• deciding whether to reuse, extend, split, merge, or create a worker
• defining worker purpose, ownership, and non-goals
• shaping the skill, tool, runtime, and permission loadout for a recurring job
• designing handoff contracts between adjacent workers
• auditing a roster for overlap, gaps, ambiguity, or sprawl
• clarifying which tasks a worker should accept, refuse, or escalate
• turning vague specialist ideas into operational role definitions

Do not use this skill for