parallel-explore

Parallel exploration uses git worktrees to create isolated workspaces for each approach, allowing rapid comparison and reducing bias from a single-path decision. It guides teams from the decision point through evaluation and merge.

Git worktrees are needed when several viable architecture paths or library designs exist and rapid comparison is required. They provide independent environments to test conflicting approaches simultaneously without corrupting the main branch.

Run the parallel-explorer script with a task description and a list of approaches. Check progress using the status command, evaluate results, merge the chosen approach, and finally cleanup the worktrees.

Yes, the parallel exploration workflow supports nested exploration decisions and maintains a trace of exploration decisions in logs. It also records detailed outcomes in an EXPLORATION_RESULT.md file within each worktree.

Use the evaluate command to compare the EXPLORATION_RESULT.md files from each worktree, then execute the merge command with the chosen approach name to integrate the winning path back into the main project workspace.

You need the parallel-explorer script and an existing project workspace. The skill operates by creating isolated git worktrees within your repository to test various implementation approaches independently.