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>

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.

3 hooks across 3 events