Aha-Loop
CLAUDE.md181 starsChanged 9 months agoMITView on GitHub
This is the Aha Loop project - a fully autonomous AI development system that extends Ralph with planning, research, and oversight capabilities. This project uses Aha Loop, a fully autonomous AI development system with: - Interactive vision building - Parallel exploration via git worktrees - Full observability and thought logging - Automatic skill creation and maintenance - Unlimited resource access - God Committee - Independent oversight layer with supreme authority Aha Loop can operate on any project without copying files.…
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architectSkill
- doc-reviewSkill
- god-consensusSkill
- god-interventionSkill
- god-memberSkill
- observabilitySkill
- parallel-exploreSkill
- plan-reviewSkill
- prd-converterSkill
- prdSkill
- researchSkill
- roadmapSkill
- skill-creatorSkill
- vision-builderSkill
- visionSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
14 rules. About 0 are common, 10 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 85
When facing significant decisions, explore multiple approaches:
- Very specific: line 103
All skills are in .claude/skills/:
- Distinctive: line 196
When you learn something reusable:
- Distinctive: line 204
When you notice a repetitive workflow:
- Distinctive: line 213
Log your thoughts: - Use observability skill
- Distinctive: line 214
Explore in parallel: - When facing decisions
- Distinctive: line 215
Latest versions: - Always prefer latest stable
- Distinctive: line 216
Document learnings: - Update knowledge base
- Distinctive: line 218
Maintain docs: - Run doc-cleaner after milestones
- Distinctive: line 245
When you are awakened as a committee member (Alpha, Beta, or Gamma):
- Very specific: line 247
Observe: - Use ./scripts/god/observer.sh to assess system state
- Distinctive: line 249
Deliberate: - Create proposals, vote on decisions
- Very specific: line 250
Intervene: - Use ./scripts/god/powers.sh when needed
- Very specific: line 354
Read the full skills at .claude/skills/god-member/SKILL.md, .claude/skills/god-consensus/SKILL.md, and …
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Aha Loop - Claude Code Instructions
Project Overview
This is the Aha Loop project - a fully autonomous AI development system that extends Ralph with planning, research, and oversight capabilities.
Aha Loop Autonomous Development System
This project uses Aha Loop, a fully autonomous AI development system with:
- Interactive vision building
- Parallel exploration via git worktrees
- Full observability and thought logging
- Automatic skill creation and maintenance
- Unlimited resource access
- God Committee - Independent oversight layer with supreme authority
Starting a New Project
Workspace Mode (Recommended for External Projects)
Aha Loop can operate on any project without copying files. All Aha Loop data is stored in .aha-loop/ within your project:
# Initialize workspace in your project
/path/to/aha-loop/scripts/aha-loop/orchestrator.sh --init-workspace /path/to/your-project
# Run Aha Loop on your project
/path/to/aha-loop/scripts/aha-loop/orchestrator.sh --workspace /path/to/your-project --build-vision
# Or set environment variable
export AHA_LOOP_WORKSPACE=/path/to/your-project
/path/to/aha-loop/scripts/aha-loop/orchestrator.sh --build-vision
# Or run from within your project (auto-detects .aha-loop/)
cd /path/to/your-project
/path/to/aha-loop/scripts/aha-loop/orchestrator.sh --build-visionWorkspace Directory Structure:
your-project/
├── .aha-loop/ # All Aha Loop files here
│ ├── config.json
│ ├── prd.json
│ ├── progress.txt
│ ├── project.vision.md
│ ├── project.roadmap.json
│ ├── research/
│ ├── exploration/
│ ├── knowledge/
│ ├── logs/
│ └── .god/
├── src/ # Your code (untouched)
└── ...Interactive Vision Building (Recommended)
./scripts/aha-loop/orchestrator.sh --build-visionYou'll be guided through questions to build a complete vision.
Manual Vision
cp scripts/aha-loop/templates/project.vision.template.md project.vision.md
# Edit the file
./scripts/aha-loop/orchestrator.sh --tool claudeWorkflow Phases
Vision → Architecture → Roadmap → [PRD Execution Loop]
│
Research → Plan Review → Implement → QA
▲ │
└──────────────────────────────┘Parallel Exploration
When facing significant decisions, explore multiple approaches:
# Let AI suggest approaches
./scripts/aha-loop/parallel-explorer.sh explore "authentication strategy"
# Specify approaches
./scripts/aha-loop/parallel-explorer.sh explore "database layer" --approaches "sqlx,diesel,sea-orm"
# Evaluate results
./scripts/aha-loop/parallel-explorer.sh evaluate explore-xxx
# Merge best approach
./scripts/aha-loop/parallel-explorer.sh merge explore-xxx chosen-approachSkills Location
All skills are in .claude/skills/:
| Skill | File | Purpose |
| vision | vision/SKILL.md | Parse project goals |
| vision-builder | vision-builder/SKILL.md | Interactive vision building |
| architect | architect/SKILL.md | Design tech stack |
| roadmap | roadmap/SKILL.md | Plan milestones |
| parallel-explore | parallel-explore/SKILL.md | Guide parallel exploration |
| skill-creator | skill-creator/SKILL.md | Create new skills |
| doc-review | doc-review/SKILL.md | Review documentation |
| observability | observability/SKILL.md | Log AI thoughts |
| god-member | god-member/SKILL.md | God Committee member behavior |
| god-consensus | god-consensus/SKILL.md | Consensus building |
| god-intervention | god-intervention/SKILL.md | Intervention execution |
Key Commands
# Main orchestrator
./scripts/aha-loop/orchestrator.sh --tool claude
./scripts/aha-loop/orchestrator.sh --build-vision
./scripts/aha-loop/orchestrator.sh --explore "task"
./scripts/aha-loop/orchestrator.sh --maintenance
# Parallel exploration
./scripts/aha-loop/parallel-explorer.sh explore "task"
./scripts/aha-loop/parallel-explorer.sh status
./scripts/aha-loop/parallel-explorer.sh evaluate explore-xxx
./scripts/aha-loop/parallel-explorer.sh cleanup --all
# Skill management
./scripts/aha-loop/skill-manager.sh list
./scripts/aha-loop/skill-manager.sh create my-skill
./scripts/aha-loop/skill-manager.sh review
# Documentation
./scripts/aha-loop/doc-cleaner.sh --report
./scripts/aha-loop/doc-cleaner.sh --fixObservability
Log your thoughts to logs/ai-thoughts.md:
## 2026-01-29 14:30:00 | Task: PRD-003 | Phase: Research
### Inner Thoughts
I'm researching authentication strategies...
### Decision Point
- Considering: JWT
- Considering: Session
- **Chosen:** JWT because...
### Next Action
Will implement the token generation...Resource Access
You have unlimited access to:
- Docker containers
- Full filesystem
- Network requests
- Parallel worktrees
Never hold back due to resource concerns.
Library Versions
Always use the latest stable version.
# Check latest Rust crate
curl -s "https://crates.io/api/v1/crates/tokio" | jq '.crate.max_stable_version'
# Check latest npm package
npm view react versionCode Quality
# Rust
cargo check # Type check
cargo clippy # Lint
cargo test # TestKnowledge Base
When you learn something reusable:
- Project-specific →
knowledge/project/patterns.md - Architecture decisions →
knowledge/project/decisions.md - Gotchas →
knowledge/project/gotchas.md - General knowledge →
knowledge/domain/[topic]/
Creating New Skills
When you notice a repetitive workflow:
./scripts/aha-loop/skill-manager.sh create my-new-skill
# Edit .claude/skills/my-new-skill/SKILL.mdImportant Rules
- Log your thoughts - Use observability skill
- Explore in parallel - When facing decisions
- Latest versions - Always prefer latest stable
- Document learnings - Update knowledge base
- Create skills - Codify repetitive workflows
- Maintain docs - Run doc-cleaner after milestones
- Never give up - You have unlimited resources
God Committee
An independent oversight layer with supreme authority.
Awakening the Committee
# Random topic awakening
./scripts/god/awakener.sh random
# Critical situation
./scripts/god/awakener.sh critical "system failure detected"
# Single member
./scripts/god/awakener.sh single alpha "code quality review"
# Run as daemon (background)
./scripts/god/awakener.sh daemonAs a Committee Member
When you are awakened as a committee member (Alpha, Beta, or Gamma):
- Observe - Use
./scripts/god/observer.shto assess system state - Communicate - Acquire lock, send messages, release lock
- Deliberate - Create proposals, vote on decisions
- Intervene - Use
./scripts/god/powers.shwhen needed
Observer Commands
# Take a full system state snapshot
./scripts/god/observer.sh snapshot
# Continuous monitoring mode
./scripts/god/observer.sh watch [interval]
# Run health checks
./scripts/god/observer.sh check
# Check for anomalies
./scripts/god/observer.sh anomaly
# Show recent events
./scripts/god/observer.sh timeline [count]
# Generate full observation report
./scripts/god/observer.sh report
# Add custom timeline event
./scripts/god/observer.sh event TYPE DESCRIPTIONPowers Available
# Pause execution
./scripts/god/powers.sh pause "investigation needed"
# Resume execution
./scripts/god/powers.sh resume
# Terminate processes
./scripts/god/powers.sh terminate all
# Git rollback
./scripts/god/powers.sh rollback HEAD~3 soft
# Auto-repair
./scripts/god/powers.sh repair allConsensus Rules
- Standard actions: 2/3 majority required
- Emergency actions: 1 member can act, report later
- Actions requiring consensus: termination, major rollback, skill deletion
Committee Communication
# Check council status
./scripts/god/council.sh status
# Acquire speaking rights
./scripts/god/council.sh lock YOUR_ID
# Send message
./scripts/god/council.sh send YOUR_ID "recipients" "type" "subject" "body"
# Create proposal
./scripts/god/council.sh propose YOUR_ID "type" "description" "rationale"
# Vote
./scripts/god/council.sh vote YOUR_ID "decision-id" "approve|reject|abstain" "comment"
# Release speaking rights
./scripts/god/council.sh unlock YOUR_IDDirectives System
Communicate decisions to the execution layer:
# Publish directive (mandatory - critical ones pause execution)
./scripts/god/council.sh publish YOUR_ID directive critical "Security issue found in X"
# Publish guidance (suggestion - included in AI context)
./scripts/god/council.sh publish YOUR_ID guidance normal "Consider approach Y for Z"
# Publish summary (context from discussions)
./scripts/god/council.sh publish YOUR_ID summary normal "Decided to use pattern X"
# Mark directive complete
./scripts/god/council.sh complete DIRECTIVE_ID
# View all directives
./scripts/god/council.sh directivesGit Hook Integration
Auto-awaken committee on commits:
./scripts/god/install-hooks.sh # Install
./scripts/god/install-hooks.sh --uninstall # RemoveRead the full skills at .claude/skills/god-member/SKILL.md, .claude/skills/god-consensus/SKILL.md, and .claude/skills/god-intervention/SKILL.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

