Designs system architecture and selects technology stack based on vision analysis. Use after vision analysis for technical decisions. Triggers on: design architecture, select tech stack, choose framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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:
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Designs system architecture and selects technology stack based on vision analysis. Use after vision analysis for technical decisions. Triggers on: design architecture, select tech stack, choose framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews and cleans up outdated documentation. Use periodically to maintain documentation health. Triggers on: review docs, clean up documentation, check for stale docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides God Committee members through consensus-building for collective decisions. Use for proposals, voting, and disagreement resolution. Triggers on: consensus, voting, proposal, committee decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides God Committee members through executing interventions. Use for repairs, rollbacks, and emergency actions. Triggers on: intervention, repair, rollback, emergency action.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Defines God Committee member behavior and responsibilities with oversight authority. Use when operating as a committee member. Triggers on: god committee, committee observation, council discussion.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Logs AI thoughts and decisions for human observability. Applies continuously throughout all tasks to maintain transparency.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.