unbound-force-heroes

Route natural language queries to Unbound Force swarm heroes across six-stage lifecycles.

3|11|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/unbound-force/unbound-force --skill unbound-force-heroes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unbound-force-heroes
Source: https://github.com/unbound-force/unbound-force/tree/main/.opencode/skill/unbound-force-heroes
Command: npx skills add https://github.com/unbound-force/unbound-force --skill unbound-force-heroes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a swarm of AI-hero personas (Muti-Mind, Cobalt-Crush, Gaze, The Divisor, Mx F) to route natural language queries to the correct hero and manage a six-stage feature lifecycle.

Core Features & Use Cases

  • Route natural language queries to the correct hero and trigger their stage-specific tasks within the swarm.
  • Define, implement, validate, review, accept, and reflect workflow stages with autonomous delegation and human checkpoints.
  • Leverage Dewey context queries to ground decisions in project history and provide provenance for artifacts.

Quick Start

Route a feature inquiry to Muti-Mind to begin the define stage.

Frequently Asked Questions about unbound-force-heroes

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

FAQPage Schema
How do I route natural language queries to coordinate AI personas for product development?

You can route natural language queries to an AI swarm by delegating tasks to specific hero personas. This skill identifies the correct hero and triggers stage-specific tasks to coordinate product owner, developer, and tester roles across a feature lifecycle.

What is the best way to manage a six-stage feature lifecycle with autonomous delegation?

Managing a six-stage feature lifecycle requires routing tasks through define, implement, validate, review, accept, and reflect stages. This skill coordinates swarm delegation to automate these stages while maintaining human checkpoints for quality assurance.

How does Dewey context querying work for grounding decisions in project history?

Dewey context queries ground decisions by retrieving relevant project history and providing provenance for artifacts. This mechanism ensures that swarm personas execute tasks based on established context rather than isolated reasoning.

Can I use swarm routing for tasks that require product owner, developer, and tester coordination?

Yes, swarm routing applies directly to tasks requiring product owner, developer, tester, reviewer, and manager coordination. It delegates queries to the correct hero to trigger stage-specific workflows across the development lifecycle.

Does autonomous stage execution with human checkpoints work for complex development workflows?

Autonomous stage execution with human checkpoints supports complex workflows by allowing AI personas to process stages independently while pausing for human validation. This ensures quality assurance during the define, implement, validate, and review phases.

Why does query routing fail when frontmatter-defined metadata is missing from the workflow?

Query routing depends on frontmatter-defined metadata to correctly identify heroes and map stages. Without this metadata, the swarm cannot determine the appropriate persona delegation or trigger the correct lifecycle stage for the incoming request.