reactive-loop

Coordinate role-specific agents across define, design, implement, verify, and fix phases.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/antoinersw/pbi-versioning --skill reactive-loop-antoinersw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reactive-loop
Source: https://github.com/antoinersw/pbi-versioning/tree/main/.claude/skills/reactive-loop
Command: npx skills add https://github.com/antoinersw/pbi-versioning --skill reactive-loop-antoinersw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a self-correcting multi-agent workflow that coordinates cross-functional agents to deliver software features with automatic routing and collaboration.

Core Features & Use Cases

  • Initialize and maintain a shared state to track workflow phase, retry counts, and agent history.
  • Spawn and coordinate role-specific agents (PO, Architect, Frontend Engineer, QA, Dev) across the define -> design -> implement -> verify -> fix phases.
  • Implement deterministic task routing, error taxonomy, and automatic retries to accelerate delivery while improving quality.
  • Provide end-to-end visibility with a recoverable loop that learns from failures and updates the process over time.

Quick Start

Invoke /reactive-loop to start a feature and follow the prompts to define the user story, then watch the agents collaborate automatically.

Frequently Asked Questions about reactive-loop

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

FAQPage Schema
How do I automate a multi-agent workflow for software feature delivery?

You can automate a multi-agent workflow by initializing a shared state to coordinate role-specific agents across define, design, implement, verify, and fix phases. The system handles deterministic task routing and automatic retries to accelerate feature delivery.

What is a self-correcting multi-agent orchestration loop?

A self-correcting multi-agent loop is a workflow that coordinates cross-functional agents to deliver software features. It uses an error taxonomy and state management to route failures, automatically spawning retries and updating the process over time.

How does error routing work in automated multi-agent workflows?

Error routing in automated workflows uses a defined error taxonomy to handle failures during task execution. It automatically routes errors to the appropriate fix phase, updates retry counts in the shared state, and re-runs the failed step.

Can I use role-specific agents for quality assurance and feature implementation?

Yes, you can spawn role-specific agents such as PO, Architect, Frontend Engineer, QA, and Dev. The orchestration loop coordinates these agents sequentially and dynamically across verification and implementation phases to ensure quality assurance.

How do I start a self-correcting loop to coordinate cross-functional agents?

To start a self-correcting loop, invoke the command and follow the prompts to define your user story. Once defined, the shared state initializes and the role-specific agents collaborate automatically across the delivery phases.

When do I need dynamic agent spawning for task orchestration?

You need dynamic agent spawning when coordinating complex feature delivery that requires cross-functional collaboration. It allows the workflow to spawn the exact role-specific agents needed for each phase while maintaining a recoverable loop with end-to-end visibility.