skills.rest
getspur
getspurOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spurpower-worker-signals

Standardize blocker, scope change, and risk reports from coding agents as JSON sentinels.

2|Updated Apr 15, 2026
Search Tags:#workflow#agents#orchestration#signals#error-reporting#spur
One-click install
npx skills add https://github.com/getspur/spur --skill spurpower-worker-signals
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spurpower-worker-signals
Source: https://github.com/getspur/spur/tree/main/.claude/skills/spurpower-worker-signals
Command: npx skills add https://github.com/getspur/spur --skill spurpower-worker-signals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of ephemeral and unstructured communication between delegated coding agents and the central orchestrator, ensuring that blockers, scope creep, and risks are captured in a durable, actionable format.

Core Features & Use Cases

  • Structured Signal Emission: Provides a standardized protocol for agents to report scope drift, blockers, and design risks using specific JSON sentinels and issue labels.
  • Deduplication Logic: Prevents redundant reporting by requiring unique signal IDs and checking for existing processed signals.
  • Use Case: When an agent discovers that a task requires modifying files outside the original scope, it uses this skill to emit a scope_drift signal, allowing the orchestrator to pause work and re-plan effectively.

Quick Start

Use the spurpower-worker-signals skill to emit a scope drift signal when you encounter unexpected complexity that requires a change in the original task plan.

Frequently Asked Questions about spurpower-worker-signals

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

FAQPage Schema
How do I standardize agent communication for error reporting in a multi-agent workflow?▼

You can standardize agent communication by applying specific JSON sentinel formats and issue labeling conventions, which capture blockers and architectural risks from delegated coding agents into a durable, actionable format for a central orchestrator.

When do I need to emit a scope drift signal in multi-agent orchestration?▼

You need to emit a scope drift signal when a delegated coding agent discovers that a task requires modifying files outside the original scope, allowing the orchestrator to pause work and re-plan the architectural approach effectively.

Can I use this skill to prevent redundant error reporting from multiple coding agents?▼

Yes, the skill prevents redundant reporting by requiring unique signal IDs and checking for existing processed signals, ensuring that blockers and scope changes are not duplicated in the central orchestrator's state management.

What is the best way to report architectural risks from delegated agents to an orchestrator?▼

The best way to report architectural risks is to use structured signal emission with specific JSON sentinels, ensuring durable state management and automated processing by the brain in multi-agent development environments.

Does multi-agent error reporting require specific formats for automated processing?▼

Yes, automated processing by the orchestrator requires adherence to specific JSON sentinel formats and issue labeling conventions to ensure task visibility and durable state management for project success.

Related Skills

Explore More Software Engineering Skills→
getspurgetspur
2

worker-signals

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

Official
Advanced
NikiforovAllNikiforovAll
137

spec-driven

Coordinate subagents through spec-driven development phases with approval gates.

Community
Advanced
Harmeet10000Harmeet10000
7

langchain-architecture

Design LangChain 1.x and LangGraph architectures for agents, memory, and tool integration.

Community
Advanced
amdmaxamdmax
2

create-story

Creates minimal GitHub issues from staged changes using the GitHub CLI.

Community
Intermediate