.ralph/ directory with configuration, prompts, guides, and scripts tailored to your codebase.
What happens
The init process has six phases:Scanning
Wiggum runs parallel detectors across your project to identify your tech stack. Detects 80+ technologies including:
- Core — Framework, package manager, testing (unit + E2E), styling
- Data — Database, ORM, API layer
- Frontend — State management, UI components, form handling
- Services — Auth, analytics
- Infra — Hosting, CI/CD, MCP servers
API key
Enter your API key. Wiggum saves it to
.ralph/.env.local (gitignored) so you don’t need to re-enter it.Model selection
Pick models for each purpose:
- Planning model (e.g. Opus) — Handles spec generation, architectural decisions, and verification
- Implementation model (e.g. Sonnet) — Handles the coding loop
AI analysis
Wiggum runs an agentic analysis of your codebase, producing structured context:
- Entry points and key files
- Directory purposes
- Build, dev, test, lint commands
- Naming conventions
- Project-specific implementation guidelines
Flags
AI provider to use. Options:
anthropic, openai, openrouter.Stay in interactive TUI mode after init completes.
Accept all defaults and skip confirmation prompts.
Output
Creates the.ralph/ directory:
Examples
To rescan your project after changes without repeating the full init flow, use
wiggum sync.
