factory-workflow

Orchestrate cross-agent factory runs for software feature requests.

3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/gulati8/justice-league-factory --skill factory-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-workflow
Source: https://github.com/gulati8/justice-league-factory/tree/main/.claude/skills/factory-workflow
Command: npx skills add https://github.com/gulati8/justice-league-factory --skill factory-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates cross-agent collaboration to plan, execute, and review Justice League factory runs by codifying roles, artifact contracts, multi-phase dispatch, autonomy gates, and failure handling. Injected into Batman's context — not user-invocable and designed for deterministic, auditable workflows.

Core Features & Use Cases

  • Defines the agent team, their responsibilities, tools, and expected outputs.
  • Standardizes artifacts and contracts (e.g., .factory-run artifacts and .claude/schemas) to enable reliable handoffs.
  • Provides autonomy gates (spec, plan, ship) with escalation paths, proactive problem surfacing, and configurable overrides.
  • Enables traceable runs with a unique factory_run_id, telemetry hooks, and structured artifact contracts.

Quick Start

Run a full factory pipeline for a project by supplying a feature request and gate preferences.

Frequently Asked Questions about factory-workflow

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

FAQPage Schema
How do I orchestrate multi-agent workflows for software feature development?

Multi-agent workflow orchestration coordinates cross-agent roles to plan, execute, and review end-to-end factory runs for software features. It codifies agent responsibilities, artifact contracts, and dispatch phases to enable reliable handoffs and structured governance.

What are autonomy gates in multi-agent orchestration and how do they work?

Autonomy gates are structured checkpoint mechanisms—spec, plan, and ship—that control multi-agent execution phases. They provide escalation paths, proactive problem surfacing, and configurable overrides to ensure deterministic, auditable workflows with robust governance contracts.

How do I standardize artifact handoffs between agents in a multi-agent pipeline?

Standardize artifact handoffs by defining structured artifact contracts and schemas, such as .factory-run artifacts and .claude/schemas. These contracts ensure reliable cross-agent coordination and traceable runs with unique factory_run_ids for deterministic execution.

Can I trace and audit multi-agent factory runs with unique identifiers?

Yes, multi-agent factory runs are traceable using a unique factory_run_id, telemetry hooks, and structured artifact contracts. These features inject governance and auditing capabilities directly into the workflow context for deterministic execution.

Does multi-agent orchestration require user invocation to manage factory runs?

No, multi-agent orchestration is injected directly into the coordinator context rather than being user-invocable. It is designed for deterministic, auditable workflows where cross-agent collaboration follows predefined roles and artifact contracts.

What's the best way to handle failure and escalation in multi-agent software pipelines?

Handle failure and escalation through autonomy gates that provide structured escalation paths and proactive problem surfacing. Configurable overrides allow controlled execution while maintaining robust governance contracts across cross-agent factory runs.