From waggle
Delegates a task to another organization member by updating Assignee, resetting executor fields, and recording delegation history in Context. Use this skill whenever the user wants to hand off, transfer, reassign, or give a task to someone else — even if they don't say "delegate" explicitly. Triggers on: "delegate task", "assign to", "transfer task", "reassign", "hand off", "give to", "pass to another person".
npx claudepluginhub kazukinagata/waggle --plugin waggleThis skill uses the workspace's default tool permissions.
Delegates a task to another organization member. Changes Assignee to the recipient and appends delegation history to Context.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Delegates a task to another organization member. Changes Assignee to the recipient and appends delegation history to Context.
Invoke the bootstrap-session skill to establish the active provider and current user.
Skip if active_provider and current_user are already set in this conversation.
Also invoke the looking-up-members skill to resolve org_members (needed for recipient lookup).
If the user did not specify a task clearly:
looking-up-members skill.teamMatch: true): inform "'{query}' is a team name. Assignee must be exactly 1 person. Which member of {teamName} should this be delegated to?" and present the team's member list for selection.Before delegating, verify task content is sufficient for the recipient's agent to execute:
These are non-blocking suggestions. Proceed with delegation if the user confirms.
Apply the following field updates (other fields remain unchanged).
Issuer is preserved (not modified) — it tracks the original task creator, not the current assignee.
Assignee to [recipient].assigning-to-others skill and apply the field resets it defines (this clears Acknowledged At among other fields).recipient.id == current_user.id, set Acknowledged At to the current ISO 8601 timestamp (no acknowledgment needed for self-assigned tasks).Context (see format below).Append format for the Context field:
Delegated from @{current_user.name} to @{recipient.name} on {YYYY-MM-DD}
(Optional) Confirm with the user and reset Status to Backlog (suggests re-triage).
After updating the task, push fresh data to the view server as described in the active provider's SKILL.md (Pushing Data to View Server section).
After pushing to the view server, offer to notify the recipient via Slack DM.
Skip this step if: the recipient is the current user (self-delegation).
slack_send_message, slack_search_users).
slack_search_users with the recipient's name or email.slack_send_message:You've been assigned a task: "{task title}"
Priority: {priority}
From: @{current_user.name}
Report:
Delegation complete: "{task title}" → @{recipient.name}
Delegation history has been appended to Context.
The recipient will see this task when they run managing-tasks (my tasks).
Invoke the assigning-to-others skill for the canonical field reset rules applied when assigning to another person.