worker-signals

Standardize blocker, scope drift, and architectural risk reporting in multi-agent coding environments.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/getspur/spur --skill worker-signals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worker-signals
Source: https://github.com/getspur/spur/tree/main/.spur/skills/worker-signals
Command: npx skills add https://github.com/getspur/spur --skill worker-signals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of silent failures and unmanaged scope creep in multi-agent systems by providing a structured, durable protocol for workers to report blockers, risks, and scope changes to the orchestrator.

Core Features & Use Cases

  • Structured Signal Emission: Provides a precise format for reporting scope drift, blockers, and design risks that the brain can parse automatically.
  • Durable Communication: Ensures that critical task updates are not lost in ephemeral chat logs, allowing for reliable re-planning.
  • Use Case: When a worker discovers that a task requires modifying files outside the original scope, it uses this skill to emit a scope_drift signal, triggering an immediate re-evaluation by the brain.

Quick Start

Use the worker-signals skill to report a high-severity scope drift by emitting a signal with the required JSON sentinel and adding the appropriate signal label to the issue.

Frequently Asked Questions about worker-signals

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

FAQPage Schema
How do I report scope drift and blockers in a multi-agent workflow?

You can prevent silent failures in agentic workflows by emitting structured signal metadata that standardizes communication of blockers, scope drift, and architectural risks directly to the central orchestrator for reliable re-planning.

How do I prevent silent failures and unmanaged scope creep in multi-agent systems?

You can prevent silent failures in agentic workflows by emitting structured signal metadata that standardizes communication of blockers, scope drift, and architectural risks directly to the central orchestrator for reliable re-planning.

How do I trigger automated state machine transitions during complex task execution?

Automated state machine transitions are triggered by emitting structured worker signals containing specific metadata and issue labels, which the central orchestrator parses to immediately re-evaluate and adjust the task plan.

What is the best way to ensure communication is not lost in ephemeral agent chat logs?

Worker agents can report high-severity scope drift by emitting a signal with the required JSON sentinel and adding the appropriate signal label to the issue, triggering an immediate re-evaluation by the brain.

How do I report high-severity scope drift when modifying files outside the original task scope?

Worker agents can report high-severity scope drift by emitting a signal with the required JSON sentinel and adding the appropriate signal label to the issue, triggering an immediate re-evaluation by the brain.

Can an orchestrator automatically parse architectural risks reported by worker agents?

This approach is designed specifically for multi-agent coding environments with a central orchestrator, so it may not suit simple single-agent setups that lack automated signal parsing and state machine transition capabilities.