Skip to content
Development
Skill

/fan-out

Parallel agent orchestration for OST exploration. Fan-out multiple solution explorations, fan-in results to compare and select winners.

From plugin
mycelium
4662 skills
Install
$ npx -y skills add haabe/mycelium --skill fan-out --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/fan-out

Context preview

The summary Claude sees to decide when to auto-load this skill.

Parallel agent orchestration for OST exploration. Fan-out multiple solution explorations, fan-in results to compare and select winners.

SKILL.md

fan-out.SKILL.md
name: fan-out
description: "Parallel agent orchestration for OST exploration. Fan-out multiple solution explorations, fan-in results to compare and select winners."
metadata:
  instruction_budget: "22"
  framework_dependency: "mycelium"
  framework_dependency_note: "This skill is designed to run within the Mycelium framework (https://github.com/haabe/mycelium). Standalone use will skip the canvas state, theory gates, and harness behavior the skill assumes. Install: /plugin install mycelium@haabe-mycelium."

Fan-Out / Fan-In Orchestration

When to Use

  • OST has 2+ solutions for the same opportunity that need parallel exploration
  • Independent delivery work items that can be parallelized
  • Multiple research streams needed simultaneously

Workflow

1. Prepare (Lead Agent)

  • Read .claude/canvas/opportunities.yml
  • Identify solutions needing parallel work
  • For each: identify riskiest assumption and design test

2. Fan-Out (Spawn Workers)

For each solution:

  • Spawn subagent or Agent Team member
  • Provide: clear task, read-only canvas context, worktree isolation, time bound
  • Each worker runs independently

3. Fan-In (Collect Results)

  • Collect all worker results
  • Update ICE scores in canvas
  • Run `/mycelium:bias-check` on combined findings
  • Select winner(s) based on evidence
  • Log decision in .claude/harness/decision-log.md

Leaf Bakeoff Mode

When comparing competing OST leaves for the same opportunity:

  • Each worker returns a structured **scorecard** (Four Risks + ICE + assumption test result + segment fit)
  • Lead agent applies **winner selection rules**: clear winner (>20% ICE delta), close race (tiebreaker), segment split (both advance), both fail (archive and re-evaluate)
  • Losers are archived to `.claude/canvas/archived-solutions.yml` with full evidence snapshot

See `${CLAUDE_PLUGIN_ROOT}/orchestration/leaf-bakeoff.md` for the complete bakeoff protocol.

Rules

  • Workers NEVER write to canvas (lead agent does)
  • Workers NEVER progress diamonds
  • Lead agent ALWAYS runs bias check on combined results
  • Minimum 2 workers for meaningful comparison
  • Maximum 3 leaves per bakeoff (respects L3 WIP ceiling)

See `${CLAUDE_PLUGIN_ROOT}/orchestration/agent-teams.md` for full orchestration patterns.

Read more
Ships withmycelium

A harness that asks who this is for before the agent writes code. Built on Claude Code, where the gates are structural. The files and skills port to opencode, Codex and Cursor. Outcome over output. You know how this goes.

Get the whole plugin
Stats
46
Stars
3
Forks
Active
Maintenance
Python
Language
MIT
License
3d ago
Last commit
5mo ago
Created

Repo: haabe/mycelium

Other skills on mycelium.

adopt
Skill

adopt

Bring Mycelium into a project that already has code. Detects that the repo predates the framework, asks before touching anything, then reads the codebase to…

@haabe@haabeView Skill