Documentation
Guild docs
Everything you need to install, configure, and extend Guild — from your first run to authoring custom skills.
Getting Started
Core Concepts
How It Works
-
How Guild Works
Guild's 7-step lifecycle — brainstorm, plan, build, qa, ops, reflect — runs behind three approval gates. You confirm spec, team, and plan; the rest runs unattended.
-
Context Assembly
guild:context-assemble builds a per-specialist bundle before dispatch — only the skills and wiki pages needed for this run, capped at 6 k tokens. No project-wide dumps.
-
Cost-Aware Model Tiering
Guild auto-scores each lane to cheap, mid, or powerful. You only pay for the compute the task actually needs — deterministic signals, per-lane overrides, zero-config defaults.
-
Self-Evolving Skills
Guild skills improve through a 10-step gated pipeline: paired evals, flip report, shadow mode, promotion gate. You approve every promotion — nothing auto-promotes.
-
Project Memory & Wiki Pattern
Guild builds a shared project memory under `.guild/wiki/` — decisions, standards, product knowledge — so specialists start informed across every run.
Reference
-
Configuration Reference
Complete settings.json reference — agent_mode, model tiers, SQLite index, security/secrets policy, O-3 calibration, and cross-host dispatch for Guild v2.
-
Specialist Roster
Full roster of Guild's 14 specialists — triggers, DO-NOT-TRIGGER boundaries, skills, and default model tiers for engineering, content, and commercial groups.
-
Status Line
Guild's opt-in status-line shows active lifecycle phase, loop round, cap, and restart count. Wire via ~/.claude/settings.json and GUILD_STATUSLINE=1.
-
Command Reference
Guild v2 /guild command surface — 6 phase verbs, learn, wiki, config, initiative, and maintenance commands. Includes the phase-to-skill dispatch table.