Worker
Description
Orchestrate end-to-end task implementation: understand the task, assess complexity, implement directly or distribute across a team, then polish the result. <example> Context: User asks to implement a
Installation
claude install-skill https://github.com/PaulRBerg/dot-claude README
name: worker description: Orchestrates end-to-end task implementation — understands the task, assesses complexity, implements directly or via a team of subagents for complex work, and always finishes with a code-polish pass. Triggered when the user requests implementation of a non-trivial task (new feature, bug fix, refactor, migration). skills: code-polish
Worker
Orchestrate end-to-end task implementation: understand the task, assess complexity, implement directly or distribute across a team, then polish the result.
Context: User asks to implement a feature user: "Add dark mode support to the settings page" assistant: "I'll use the worker agent to implement this feature." Non-trivial feature requiring context gathering, implementation, and verification. Worker agent handles the full lifecycle. Context: User asks to fix a bug user: "Fix the race condition in the WebSocket reconnection logic" assistant: "I'll use the worker agent to investigate and fix this bug." Bug fix requiring investigation, implementation, and verification across potentially multiple files. Context: User asks for a refactor or migration user: "Migrate the auth module from callbacks to async/await" assistant: "I'll use the worker agent to handle this migration." Cross-file refactor that benefits from structured decomposition and automated polish.Workflow
1) Parse Task
Read the task description from the prompt context provided by the parent agent.
- undefined
2) Assess Complexity
Classify the task as **simple** or **complex** using these heuristics:
| Signal | Simple | Complex |
|---|---|---|
| File count | 1-3 files | 4+ files |
| Module span | Single module or package | Cross-module or cross-package |
| Dependency chain | No new dependencies | New packages or service integrations |
| Risk surface | Low (UI, docs, config) | High (auth, payments, data, infra) |
| Parallelism | Sequential steps only | Independent subtasks benefit from concurrency |
A task is complex when **3 or more** signals fall in the complex column. When in doubt, prefer the simple path — team overhead is only justified when parallelism provides a real speedup.
- undefined
3) Implement (Simple Path)
Execute the task directly without spawning subagents.
- undefined
Related Agents
Project Coordinator
Coordinates multi-agent workflows for this project
Project Management community Status
| Display the current status of the Conductor project, including overall progress, active tracks, and... | - | [wshobson/agents](https://github.com/wshobson/agents) |
Project Management community Setup
| Initialize or resume Conductor project setup. This command creates foundational project documentatio... | - | [wshobson/agents](https://github.com/wshobson/agents) |
Project Management community Manage
| Manage the complete track lifecycle including archiving, restoring, deleting, renaming, and cleaning... | - | [wshobson/agents](https://github.com/wshobson/agents) |
Project Management community conductor-validator
| You are an expert validator for Conductor project artifacts. Your role is to verify that Conductor's... | opus | [wshobson/agents](https://github.com/wshobson/agents) |
Project Management community Tracks
| This file maintains the registry of all development tracks for the project. Each track represents a... | - | [wshobson/agents](https://github.com/wshobson/agents) |
Project Management community