Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Use when user wants to set up slime mold exploration strategy with parallel autonomy branches for genetic algorithm approach to problem-solving
Slime Mold Strategy Setup
Overview
Set up the complete "slime mold strategy" workflow for exploring problem spaces through parallel autonomy branches that cooperate like a genetic algorithm.
Core principle: Initialize autonomy workflow with slime mold philosophy: multiple parallel branches exploring different approaches, cooperating not competing, cross-pollinating insights.
When to Use
Use this skill when:
User runs /slime command
User wants to adopt slime mold strategy for exploration
Setting up parallel branch exploration with genetic algorithm approach
DO NOT use for:
Adding single goal without branch strategy (use /create-goal)
Creating additional branches in existing workflow (use /fork-iteration)
Analyzing existing branches (use /branch-status or /compare-branches)
Quick Reference
Step
Action
Tool
1. Check state
Look for existing autonomy goal
Glob
2a. Create goal
Invoke creating-a-goal skill if needed
Skill
2b. Update only
Skip to CLAUDE.md if goal exists
-
3. Update CLAUDE.md
Replace slime mold section or create file
Read, Write
4. Create branch
Invoke forking-iteration with goal name
Skill
5. Initialize iteration
Create iteration-0000 journal file
Write
6. Git commit
Commit with enhanced format and tag
Bash
Process
Step 1: Check Existing State
First, determine if autonomy workflow already exists:
# Look for any existing goal.md files
existing_goals=$(find autonomy -name "goal.md" 2>/dev/null)
if [ -n "$existing_goals" ]; then
mode="update-only"echo"Autonomy workflow already exists. Will update CLAUDE.md only."# Extract goal name from first goal found
goal_dir=$(dirname"$existing_goals" | head -1)
goal_name=$(basename"$goal_dir")
else
mode="full-setup"echo"No existing autonomy goal found. Will perform full setup."fi
Validation:
If multiple goals found, use first one alphabetically
Warn user: "Multiple goals detected, using [goal-name]"
Step 2: Create Goal (full-setup mode only)
If mode="full-setup", invoke the creating-a-goal skill:
# Only run if full-setup modeif [ "$mode" = "full-setup" ]; then# Invoke creating-a-goal skill using Skill tool
skill: "autonomy:creating-a-goal"# After skill completes, extract goal name
goal_dir=$(find autonomy -name "goal.md" -execdirname {} \; | head -1)
goal_name=$(basename"$goal_dir")
echo"Goal created: $goal_name"fi
Ensure autonomy/CLAUDE.md exists and contains current slime mold strategy documentation.
CLAUDE.md Content (exact text to use):
# Slime Mold Strategy
This project uses the "slime mold strategy" for exploring the problem space. Like a slime mold organism that extends multiple tendrils to find optimal paths, we maintain parallel autonomy branches that explore different approaches to the same goal. These branches represent a genetic algorithm: each branch is an independent experiment testing different hypotheses, strategies, or implementations.
Crucially, these branches are NOT competing—they are cooperating. All branches are part of the same organism pursuing the same goal. When branches encounter each other or when you discover useful insights in one branch, use `/analyze-branch <branch-name> <search-description>` to extract "genetic material" (learnings, patterns, solutions) and incorporate them into your current branch. Use `/compare-branches <branch-a> <branch-b>` to understand how different approaches diverged and what outcomes each achieved. Use `/list-branches` to inventory all active exploration tendrils. When ready to fork a new experimental direction, use `/fork-iteration [iteration] <strategy-name>` to create a new tendril from any point in history.
The goal is not to find the single "best" branch, but to explore the solution space thoroughly and cross-pollinate insights across branches, allowing the organism as a whole to discover optimal solutions through parallel exploration and cooperation.
Implementation:
# Check if autonomy/CLAUDE.md existsif [ -f "autonomy/CLAUDE.md" ]; then# Read existing content
existing_content=$(cat autonomy/CLAUDE.md)
# Check if slime mold section existsifecho"$existing_content" | grep -q "# Slime Mold Strategy"; thenecho"Updating existing slime mold section in CLAUDE.md"# Strategy: Replace section from "# Slime Mold Strategy" to next "# " heading or EOF# Use Read tool to get current content# Use Edit tool to replace the section# Read current file# Find start of "# Slime Mold Strategy" section# Find end (next # heading or EOF)# Replace that section with new contentelseecho"Appending slime mold section to existing CLAUDE.md"# Append new section to end of file# Use Edit tool to add content at endfielseecho"Creating new autonomy/CLAUDE.md with slime mold section"# Create new file with slime mold section# Use Write tool to create filefi
Write/Edit the slime mold section:
Use Write tool if creating new file, or Edit tool if updating existing file.
The section content is the markdown block shown above under "CLAUDE.md Content".
If mode="full-setup", create the initial autonomy branch:
# Only run if full-setup modeif [ "$mode" = "full-setup" ]; then# Invoke forking-iteration skill with goal-name as strategy-name# No iteration number specified = fork from current HEAD
skill: "autonomy:forking-iteration"
args: "$goal_name"# This creates branch: autonomy/[goal-name]# And checks out that branchecho"Created and switched to branch: autonomy/$goal_name"fi
Error Handling:
If forking-iteration fails (e.g., branch already exists)
Show error from skill
Don't create iteration 0000
Suggest: "Use /fork-iteration to create branch with different name"
If mode="full-setup", create the baseline setup iteration:
# Only run if full-setup modeif [ "$mode" = "full-setup" ]; then# Get current date in YYYY-MM-DD format
current_date=$(date +%Y-%m-%d)
# Create iteration-0000 file
iteration_file="autonomy/$goal_name/iteration-0000-$current_date.md"# Use Write tool to create file with this content:fi
Iteration 0000 Content:
# Iteration 0000 - YYYY-MM-DD## Beginning State
No previous iterations. This is the initial setup for the slime mold exploration strategy.
**Baseline Metrics:**
[Extract from goal.md metrics section, or "None established yet" if no metrics defined]
## Iteration Intention
Establish the foundation for slime mold strategy exploration:
- Define goal and success criteria
- Create initial autonomy branch
- Document exploration approach
- Prepare for iteration 0001 to begin actual work
## Work Performed### Setup Completed- Created goal: [Extract goal statement from goal.md]
- Established autonomy/CLAUDE.md with slime mold strategy documentation
- Created initial branch: autonomy/[goal-name]
- Initialized iteration tracking system
### Slime Mold Strategy Adopted- Multiple parallel branches will explore different approaches
- Branches cooperate via /analyze-branch for cross-pollination
- Use /fork-iteration to create new exploration tendrils
- Use /compare-branches to understand divergent paths
## Ending State
Autonomy workflow initialized. Ready to begin iteration 0001 with actual exploration work. Use `/start-iteration` to begin.
**Recommended next action:** Run `/start-iteration` to begin first real iteration of exploration.
Implementation:
Read autonomy/[goal-name]/goal.md to extract:
Goal statement (from first paragraph or "## Goal" section)
Metrics (from "## Metrics" or "Success Criteria" section)
Use Write tool to create iteration-0000-YYYY-MM-DD.md with content above, substituting:
YYYY-MM-DD with current date
[goal-name] with actual goal name
Goal statement and metrics from goal.md
Step 6: Git Commit and Tag (full-setup mode only)
If mode="full-setup", commit iteration 0000 with enhanced format:
# Only run if full-setup modeif [ "$mode" = "full-setup" ]; then# Stage the iteration file and CLAUDE.md
git add "autonomy/$goal_name/iteration-0000-$current_date.md"
git add "autonomy/CLAUDE.md"# Create enhanced commit message
git commit -m "$(cat <<'EOF'
journal: $goal_name iteration 0000
Established slime mold exploration strategy with initial autonomy branch.
## Journal Summary
Created goal definition for $goal_name, initialized slime mold strategy documentation in CLAUDE.md, created initial autonomy/$goal_name branch, and established iteration 0000 as baseline. Workflow ready for iteration 0001 to begin actual exploration work.
## Iteration Metadata
Status: active
Metrics: None (baseline setup)
Blockers: None
Next: Run /start-iteration to begin iteration 0001
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
EOF
)"# Create branch-aware tag
git tag -a "autonomy/$goal_name/iteration-0000" \
-m "journal: $goal_name iteration 0000"echo"Created git commit and tag: autonomy/$goal_name/iteration-0000"fi
Matches branch-aware tagging from ending-an-iteration skill
Step 7: Final Messages
Display completion message based on mode:
Full-setup mode:
Slime mold strategy initialized successfully!
✓ Goal created: [goal-name]
✓ CLAUDE.md documented slime mold strategy
✓ Branch created: autonomy/[goal-name]
✓ Iteration 0000 established as baseline
✓ Git commit and tag: autonomy/[goal-name]/iteration-0000
Next steps:
1. Run /start-iteration to begin iteration 0001
2. Use /fork-iteration <strategy-name> to create additional exploration branches
3. Use /analyze-branch to cross-pollinate insights between branches
4. Use /compare-branches to understand divergent approaches
Update-only mode:
Slime mold strategy documentation updated!
✓ CLAUDE.md updated with current slime mold strategy description
Your autonomy workflow is ready. Use these commands:
- /fork-iteration <strategy-name> - Create new exploration branch
- /list-branches - Inventory all autonomy branches
- /compare-branches <a> <b> - Compare two exploration paths
- /analyze-branch <branch> <search> - Extract insights from another branch
Important Notes
Git Repository Required
This skill requires a git repository:
Check with git rev-parse --git-dir before starting
If not in git repo, show error: "This command requires a git repository. Run 'git init' first."
Abort workflow if git not available
Idempotent Behavior
The skill is designed to be idempotent:
Safe to run multiple times
If goal exists: Only updates CLAUDE.md (doesn't recreate goal or iteration 0000)
CLAUDE.md section replacement ensures documentation stays current
Use this to update slime mold description as concept evolves
CLAUDE.md Location
File created at autonomy/CLAUDE.md (working directory, not plugin directory)
At same level as autonomy/[goal-name]/ directories
Provides project-level context for slime mold strategy
Iteration 0000 is Special
Iteration 0000 is baseline setup only
First real work iteration is 0001 (via /start-iteration)
Don't use starting-an-iteration skill for iteration 0000
Manually create the file with setup-specific content
Branch Name = Goal Name
Initial branch always named autonomy/[goal-name]
Matches goal directory name for consistency
Additional branches via /fork-iteration can use different strategy names
