worker-protocol

Define a standardized workflow protocol for coordinating orchestrated workers.

1|Updated Mar 29, 2026

Search Tags:#blockers #session #trajectory #orchestrator #task-file #worker-protocol

Ready to run

npx skills add https://github.com/nbdesai1992/software-factory --skill worker-protocol-nbdesai1992

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worker-protocol
Source: https://github.com/nbdesai1992/software-factory/tree/main/factory/skills/worker-protocol
Command: npx skills add https://github.com/nbdesai1992/software-factory --skill worker-protocol-nbdesai1992

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a standardized convention for coordinating orchestrated workers, ensuring consistent session structures, task lifecycles, and traceable executions across a project.

Core Features & Use Cases

Centralizes a session directory model (session/, phases/, tasks/) to promote predictable worker behavior and auditable progress.
Defines interfaces for task files, blockers, trajectory logs, and design-direction notes to enable reliable collaboration.
Supports multi-agent coordination by clarifying responsibilities and handoffs between orchestrator and workers.

Quick Start

Create a session/ directory at the project root and start following the worker-protocol for new tasks and phases.

Frequently Asked Questions about worker-protocol

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

FAQPage Schema

How do I coordinate orchestrated workers and track task status across a multi-agent project?▼

Coordinating orchestrated workers requires a standardized workflow protocol that defines session structures, task lifecycles, and traceable executions. This protocol uses a centralized session directory model with phases and tasks to ensure predictable worker behavior and auditable progress.

What is a session directory model for orchestrating specialized worker agents?▼

A session directory model is a standardized folder structure containing session, phases, and tasks directories at the project root. It provides predictable worker behavior by guiding progress with task files and session structures for safe, auditable multi-agent execution.

How do I record trajectory logs and blockers for decomposed tasks in an orchestrated workflow?▼

Recording trajectory logs and blockers involves updating task files within the session directory structure. The workflow protocol specifies interface contracts for task status updates, progress logs, and design-direction notes to enable reliable collaboration and traceable handoffs between orchestrator and workers.

Can I use this worker protocol for multi-agent coordination without external dependencies?▼

Yes, this worker protocol for multi-agent coordination operates without external dependencies. It relies solely on a standardized session directory structure and interface contracts to clarify responsibilities and handoffs between the orchestrator and specialized worker agents.

What is the best way to structure project handoffs between an orchestrator and worker agents?▼

The best way to structure project handoffs is to apply a standardized workflow protocol that defines interface contracts for task files and blockers. This clarifies responsibilities between the orchestrator and workers, ensuring safe and auditable execution during task decomposition.