delegation

Delegation Skill

Use this skill when another employee or engine is a better fit for a bounded piece of work. Delegate across roles; use native sub-agents only for extra hands inside your own role. Prefer the chain of command for multi-layer work, while keeping every brief and stop condition explicit.

Choose the target

1. Use list_employees for the roster, find_employees to filter by department/rank/engine, and get_employee to inspect persona, manager, and direct reports.
2. Select by role and persona fit, not novelty or a desire to spread work around. One employee can have several parallel sessions.
3. Delegate through the relevant manager when they should own decomposition and review. Direct delegation remains valid when it is the clearest route.

Tracked work versus a quick session

Use delegate_task for company work that needs ownership, status, review, or a durable record. One call uses or mints the Todo, starts the child session, and links them:

{
  "employee": "a-builder",
  "title": "Implement parser validation",
  "task": "Implement the specified validation. Acceptance: focused tests fail before the change, then the focused and full suites pass. Report changed files and command evidence.",
  "effortLevel": "medium",
  "idempotencyKey": "parser-validation-v1"
}

• Pass workItemId when an existing Todo already tracks the outcome.
• Use one stable idempotencyKey for retrying the same delegation. If a spawn fails after the Todo is minted, preserve and report the returned work-item id; do not blindly create another delegation.
• If you pass attachments, every entry must be a managed file ID returned by list_files — never workspace or absolute paths. Missing or stale managed file IDs are rejected before Jinn creates the Todo or child session. Attach only files the child genuinely needs.

Use spawn_session for a quick, untracked question or short consultation:

{
  "employee": "a-reviewer",
  "prompt": "Review this schema choice and return the top two concrete risks. Do not modify files."
}