claude-coworker

Orchestrate Claude Opus and Sonnet delegation with explicit session IDs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/thesobercoder/skills --skill claude-coworker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-coworker
Source: https://github.com/thesobercoder/skills/tree/main/claude-coworker
Command: npx skills add https://github.com/thesobercoder/skills --skill claude-coworker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates Claude-based collaboration between Opus and Sonnet to manage delegation, coordination, and deterministic continuity.

Core Features & Use Cases

  • Guided Claude delegation: decide when Opus should think, when Sonnet should execute, and how to coordinate with the main agent.
  • Enforces explicit session IDs for deterministic continuity and reproducible workflows.
  • Defines non-interactive CLI delegation rules with mandatory --dangerously-skip-permissions usage for scripted tasks.

Quick Start

Invoke Claude in Opus mode to brainstorm delegation, then continue with Sonnet execution using a durable SESSION_ID.

Frequently Asked Questions about claude-coworker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate Claude Opus and Sonnet for task delegation in a CLI?

Claude coworker orchestration delegates planning to Opus and execution to Sonnet using non-interactive CLI rules, coordinating both models through a main agent for structured task management.

What is the best way to maintain deterministic continuity across Claude sessions?

Deterministic continuity is maintained by enforcing explicit session IDs, which ensures reproducible workflows and auditable automation across multiple Claude delegation steps.

When do I need to use --dangerously-skip-permissions for Claude automation?

You need --dangerously-skip-permissions for non-interactive CLI delegation and scripted tasks, ensuring safe and auditable automation when orchestrating Claude models without manual input.

Can I use Claude delegation for architecture planning and design critique?

Yes, Claude delegation applies to tasks requiring architecture planning and design critique, guiding when Opus should think through designs and when Sonnet should execute explicit steps.

Does Claude coworker require interactive input for session orchestration?

No, Claude coworker defines non-interactive CLI delegation rules, allowing scripted automation to run without interactive input by using durable session IDs and mandatory permission skipping.