Does this skill start the work on the new branch immediately?

No, this skill focuses strictly on branch creation and setup. Once the branch is created, you should run the /start-iteration command to begin work.

How does Forking Iteration differ from standard git branching?

It automates the enforcement of autonomy naming conventions and allows you to fork directly from specific iteration tags, simplifying the transition into experimental AI-driven workflows.

What happens if I don't specify an iteration number?

If no iteration is specified, the skill defaults to forking from your current HEAD, creating a new strategy branch based on your latest changes.

Can I merge these branches back into my main branch?

While technically possible via git, the autonomy philosophy treats branches as independent experiments that share knowledge via analysis rather than traditional merges, keeping history clean.

Autonomy Forking Iteration

Name: Autonomy Forking Iteration
Author: tilmon-engineering

bytilmon-engineering

•

Developer Tools

Creates new autonomy branches from specific git iterations or current commits to enable parallel experimental development paths.

The Forking Iteration skill implements a 'slime mold strategy' for development, allowing users to spawn independent exploration branches from any point in their git history. By decoupling branch creation from iteration management, it enables developers to test alternative architectures or feature implementations without risking their current progress. The skill handles complex git logic, including resolving iteration tags, validating kebab-case naming conventions, and ensuring a clean transition to new experimental workflows.

Key Features

01Fork from specific past iterations using historical git tags

02Support for bootstrapping autonomy workflows from standard branches

03Automated kebab-case branch name normalization and validation

04Branch-specific identity tracking for distinct technical strategies

05Independent exploration paths that avoid complex merge conflicts

061 GitHub stars

Use Cases

01Exploring an alternative technical approach from a specific successful past commit

02Initializing the autonomy framework on an existing project branch

03Starting a parallel experiment while keeping the current branch state intact

Key Features

01Fork from specific past iterations using historical git tags

02Support for bootstrapping autonomy workflows from standard branches

03Automated kebab-case branch name normalization and validation

04Branch-specific identity tracking for distinct technical strategies

05Independent exploration paths that avoid complex merge conflicts

061 GitHub stars

Use Cases

01Exploring an alternative technical approach from a specific successful past commit

02Initializing the autonomy framework on an existing project branch

03Starting a parallel experiment while keeping the current branch state intact