teamwork

Clean up teamwork project

Show teamwork project status dashboard

Manually trigger project verification

Join a teamwork project as a worker teammate

Start a teamwork project with native agent team collaboration

Backend specialist worker for teamwork. API, services, database, business logic. <example> Context: Orchestrator spawns a backend worker for API and database tasks user: (spawned by orchestrator via Task()) assistant: Checks TaskList for backend tasks, claims API endpoint task, implements endpoint with database integration and validation, runs tests, collects evidence (curl output, test results with exit codes), marks task completed, reports to orchestrator via SendMessage </example>

DevOps specialist worker for teamwork. CI/CD, deployment, infrastructure, containerization. <example> Context: Orchestrator spawns a devops worker for infrastructure tasks user: (spawned by orchestrator via Task()) assistant: Checks TaskList for devops tasks, claims Docker configuration task, creates Dockerfile with multi-stage build, adds docker-compose.yml, tests build succeeds, collects evidence (build logs, container runs with exit codes), marks completed, reports to orchestrator via SendMessage </example>

Documentation specialist worker for teamwork. README, API docs, examples, guides. <example> Context: Orchestrator spawns a docs worker for documentation tasks user: (spawned by orchestrator via Task()) assistant: Checks TaskList for docs tasks, claims API documentation task, reads implemented API endpoints, creates comprehensive API.md with endpoint documentation, verifies examples match implementation, collects evidence (file created, examples tested with exit codes), marks completed, reports to orchestrator via SendMessage </example>

Final project verifier for teamwork. Reads all tasks, verifies evidence, runs full build and tests. <example> Context: Orchestrator spawns final-verifier after all tasks are completed user: (spawned by orchestrator via Task()) assistant: Reads all tasks via TaskList, verifies each task has status completed with concrete evidence, scans changed files for blocked patterns, runs full project build and test suite, sends PASS/FAIL verdict to orchestrator via SendMessage with detailed findings </example>

Frontend specialist worker for teamwork. UI, components, styling, user interactions. <example> Context: Orchestrator spawns a frontend worker for UI component tasks user: (spawned by orchestrator via Task()) assistant: Checks TaskList for frontend tasks, claims component creation task, implements React component with TypeScript and styling, verifies component renders without errors, collects evidence (file created, build passes, tests pass with exit codes), marks completed, reports to orchestrator via SendMessage </example>

Use for orchestrating entire teamwork project lifecycle from planning to completion. Operates as a **team lead in delegate mode** -- coordinates via native teammate API, never writes code directly. Use this agent when coordinating complete teamwork projects that require planning, worker spawning, and verification. Examples: <example> Context: User wants to build a full-stack application with teamwork user: "/teamwork \"build full-stack app with auth and API\" --plans docs/api-spec.md" assistant: Spawns orchestrator agent. Explores codebase (Read, Glob, Grep). Decomposes goal into tasks via TaskCreate. Sets dependencies via TaskUpdate(addBlockedBy). Presents plan to user for review. On approval, creates team via TeamCreate, spawns role-specific workers via Task(teamwork:backend), Task(teamwork:frontend), etc. Assigns tasks via TaskUpdate(owner). Receives completion messages from teammates. When all tasks done, spawns Task(teamwork:final-verifier). Reports project completion. <commentary> The orchestrator operates in delegate mode: it plans and coordinates but never implements code. Workers are spawned as native teammates using Task(), and coordination happens via SendMessage and hook-driven events (TeammateIdle, TaskCompleted). </commentary> </example> <example> Context: Task verification fails user: "Continue orchestration after verification failed" assistant: Spawns orchestrator agent. Reads final-verifier report. Creates fix tasks via TaskCreate with appropriate dependencies. Spawns additional workers if needed via Task(). Monitors completion. Re-runs final verification. <commentary> The orchestrator handles verification failures by creating fix tasks and spawning workers to address them. No wave system is involved -- dependency resolution is handled natively via addBlockedBy. </commentary> </example>

Code review specialist worker for teamwork. Code quality, refactoring, best practices. <example> Context: Orchestrator spawns a review worker for code quality tasks user: (spawned by orchestrator via Task()) assistant: Checks TaskList for review tasks, claims refactoring task, explores code with symbol tools, identifies duplicate code and performance issues, refactors into reusable functions, verifies tests still pass, collects evidence (complexity reduced, tests pass with same count, exit codes), marks completed, reports to orchestrator via SendMessage </example>

Security specialist worker for teamwork. Auth, permissions, input validation, OWASP patterns. <example> Context: Orchestrator spawns a security worker for auth and validation tasks user: (spawned by orchestrator via Task()) assistant: Checks TaskList for security tasks, claims JWT authentication task, creates auth middleware with token validation, adds input sanitization, tests with valid/invalid tokens, verifies unauthorized access blocked, collects evidence (auth flow works, invalid tokens rejected with 401, exit codes), marks completed, reports to orchestrator via SendMessage </example>

Test specialist worker for teamwork. Unit tests, integration tests, fixtures, mocks. <example> Context: Orchestrator spawns a test worker for test writing tasks user: (spawned by orchestrator via Task()) assistant: Checks TaskList for test tasks, claims unit test creation task, explores implementation code, creates comprehensive test suite with edge cases and error paths, runs npm test, verifies all tests pass, collects evidence (test output with pass counts, exit codes), marks completed, reports to orchestrator via SendMessage </example>

Generic worker for teamwork. Claims and completes tasks using native API. <example> Context: Orchestrator spawns a generic worker to handle available tasks user: (spawned by orchestrator via Task()) assistant: Checks TaskList for available tasks, claims first unblocked task via TaskUpdate, reads task description, implements solution using Read/Write/Edit/Bash, collects concrete evidence, appends evidence to task description via TaskUpdate, marks task completed, sends completion report via SendMessage to orchestrator </example>

Event-driven coordination for teamwork orchestrators. Replaces polling-based monitoring loop with TeammateIdle and TaskCompleted hooks.

Hybrid task decomposition strategy for teamwork projects. Covers plan-based and semantic decomposition, granularity rules, role assignment, dependency management, and complexity assessment.

Reset and clean up teamwork project state. Use when project is stuck, failed, or needs a fresh start. Uses native TeamDelete API for cleanup.

8-phase task execution lifecycle for teamwork workers using native Claude Code APIs. Covers task discovery, claiming, structured description parsing, TDD workflow, implementation, verification, selective commit, and completion reporting.

1 hook across 1 event