execute

Coordinate multi-agent Epic execution by loading config and running stories in dependency order.

1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/firefly-events/plugin-hive --skill execute-firefly-events
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/firefly-events/plugin-hive/tree/main/skills/execute
Command: npx skills add https://github.com/firefly-events/plugin-hive --skill execute-firefly-events

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate multi-agent Epic execution by loading epic config, orchestrating pre/post-exec triggers, and executing stories in dependency order.

Core Features & Use Cases

  • Pre-exec and post-exec escalation handling, including topological sorting of stories and method-based workflow routing.
  • Agent-team vs sequential execution modes, sidecar injection, and episode recording.
  • Support for multiple methodologies to control phase ordering and cross-agent coordination.

Quick Start

Invoke the skill with an epic ID and optional flags (e.g., --methodology tdd|classic|bdd, --sequential) to execute the epic through its planned stories.

Frequently Asked Questions about execute

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

FAQPage Schema
How do I coordinate multi-agent execution for an epic broken into stories?▼

Coordinate multi-agent epic execution by loading epic config and orchestrating pre/post-exec triggers. It executes stories in dependency order using agent teams, sequential steps, and sidecar injections.

How does topological sorting handle story dependencies during workflow orchestration?▼

Topological sorting maps story dependencies to determine execution sequence for an epic. This ensures prerequisite stories complete before downstream stories run, preventing circular dependency failures.

Can I use sequential execution mode instead of agent teams for my workflow?▼

Yes, sequential execution mode processes stories step-by-step instead of deploying parallel agent teams. Toggle this mode using the --sequential flag when invoking epic execution.

What methodologies are supported to control phase ordering and agent coordination?▼

Supported methodologies include TDD, classic, and BDD options to control phase ordering and cross-agent coordination. Specify the desired methodology using the --methodology flag during execution.

When should I use sidecar injection in multi-agent workflow orchestration?▼

Use sidecar injection to introduce auxiliary capabilities into multi-agent workflow orchestration without modifying core execution logic. It supports recovery mechanisms and episode recording during epic execution.

Why is pre-exec and post-exec escalation handling needed for epic execution?▼

Pre-exec and post-exec escalation handling intercepts workflow triggers before and after story execution to manage errors and route methodologies. This ensures proper phase ordering and agent coordination throughout the epic lifecycle.