Guides parallel exploration of multiple implementation approaches using git worktrees. Use when facing decisions with multiple valid paths. Triggers on: explore options, compare approaches, parallel exploration.
Guide the process of exploring multiple implementation approaches simultaneously using git worktrees.
When you encounter a significant decision:
## Decision Point Identified
**Question:** [What needs to be decided]
**Context:** [Why this matters]
**Approaches to Explore:**
1. [Approach A] - [Brief description]
2. [Approach B] - [Brief description]
3. [Approach C] - [Brief description]
**Exploration Value:** [Why parallel exploration helps here]
Use the parallel explorer script:
./scripts/aha-loop/parallel-explorer.sh explore "task description" --approaches "approach1,approach2,approach3"
Or let AI suggest approaches:
./scripts/aha-loop/parallel-explorer.sh explore "task description"
# AI will suggest approaches automatically
In each worktree, the AI should:
Each worktree must have EXPLORATION_RESULT.md:
# Exploration Result: [Approach Name]
## Summary
[What was implemented]
## Implementation Details
- [Key implementation decisions]
- [Code structure choices]
- [Dependencies used]
## Pros Discovered
- [Pro 1]
- [Pro 2]
- ...
## Cons Discovered
- [Con 1]
- [Con 2]
- ...
## Code Quality Assessment
- Maintainability: [1-10]
- Readability: [1-10]
- Testability: [1-10]
- Performance: [1-10]
## Unexpected Findings
[Anything surprising learned during implementation]
## Recommendation Score
[1-10] - [Brief justification]
## Would Need If Chosen
[What additional work would be needed to production-ready this approach]
After all explorations complete:
./scripts/aha-loop/parallel-explorer.sh evaluate explore-task-12345
This triggers multiple evaluation agents who:
./scripts/aha-loop/parallel-explorer.sh merge explore-task-12345 chosen-approach
./scripts/aha-loop/parallel-explorer.sh cleanup explore-task-12345
You have unlimited computational resources. Don't hold back:
Each approach should be explored genuinely:
Even "losing" approaches provide value:
# Start exploration
./scripts/aha-loop/parallel-explorer.sh explore "description" --approaches "a,b,c"
# Check status
./scripts/aha-loop/parallel-explorer.sh status
./scripts/aha-loop/parallel-explorer.sh status explore-task-12345
# Evaluate completed explorations
./scripts/aha-loop/parallel-explorer.sh evaluate explore-task-12345
# List all worktrees
./scripts/aha-loop/parallel-explorer.sh list
# Merge chosen approach
./scripts/aha-loop/parallel-explorer.sh merge explore-task-12345 chosen-approach
# Cleanup
./scripts/aha-loop/parallel-explorer.sh cleanup explore-task-12345
./scripts/aha-loop/parallel-explorer.sh cleanup --all
You're implementing user authentication and there are multiple valid approaches.
./scripts/aha-loop/parallel-explorer.sh explore "user authentication for web app" \
--approaches "jwt-stateless,session-based,magic-link"
Implement full JWT authentication:
Create EXPLORATION_RESULT.md documenting:
Implement session-based auth:
Create EXPLORATION_RESULT.md documenting:
Implement passwordless magic link:
Create EXPLORATION_RESULT.md documenting:
Multiple evaluation agents review all three approaches and produce:
./scripts/aha-loop/parallel-explorer.sh merge explore-auth-12345 session-based
During exploration, you may discover new decision points. You can:
For nested exploration, create a sub-directory:
.worktrees/
explore-auth-12345/
jwt/
.worktrees/ # Nested exploration
explore-refresh-67890/
rotating-tokens/
sliding-window/
Log exploration decisions to logs/ai-thoughts.md:
## 2026-01-29 14:00:00 | Task: PRD-003 | Phase: Exploration
### Decision Point
Authentication strategy needs to be determined.
### Approaches Being Explored
1. JWT (stateless)
2. Session-based (stateful)
3. Magic link (passwordless)
### Exploration Status
Started parallel exploration: explore-auth-12345
### Expected Outcome
Will evaluate all three and merge best approach.
Before starting exploration:
During exploration:
After exploration:
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer