Guild Stack
Documentation
One page per topic. Every page starts with the short version, usually a command you can run, then goes deeper on the same page: a Power layer for detailed control, and an Architect layer for what happens underneath.
Get started
- Install and first run Install Guild Stack v3.0.0, run your first task, and check the result. Then: updates, release channels, install flags, and what the install receipt proves.
- Core concepts The handful of ideas you need to use Guild Stack, a plain-words glossary of every term on this site, and the system architecture underneath.
- Migrate to v3 Move from Guild Stack v2 to v3.0.0: the command fold, the print-only aliases, the assembler skills, and the historical v1-to-v2 guide.
- Troubleshooting and FAQ Short answers to common first questions, fixes for the problems new users hit most, known issues in 3.0.0, and how to debug a run from its records.
Work
- Lifecycle The six Guild Stack phases from init to ops, how a vague idea is routed into the product loop, how QA picks its checks, and how verify-done closes a run.
- Commands All 13 Guild Stack v3 commands with sub-verbs and flags, the retired v2 spellings and their v3 routes, and how a command dispatches to its assembler skill.
- Skills The 17 host-indexed assembler skills, how Guild Stack evolves its own guidance behind a promotion gate, and the rules an extension must meet.
- Teams and specialists How Guild Stack composes a team you approve, scores each lane to the cheapest viable model tier, dispatches ephemeral agents, and collects receipt files.
- Knowledge How Guild Stack learns your codebase, keeps a project wiki with gated promotion, recalls what it knows, and assembles bounded context for each lane.
Trust
- Review and gates The host, advisory, and adversarial roles, cross-host review with round caps and skip enforcement, and the gates a change passes on its way to stable.
- Conformance and evidence How you know a Guild Stack release is good: the release model from next to main, the 31-scenario conformance evidence, signing, and the identity records.
- Security and trust What Guild Stack is trusted to run, what it never does, secrets scrubbing and fail modes, MCP description pinning, and the PreToolUse policy gate.
Control
- Configuration Edit Guild Stack policy with /guild:config, the full key reference with defaults and fail-closed rules, and capability localization for project-owned roles.
- Hosts and adapters The two live-verified hosts, the hooks and MCP servers Guild Stack wires into a session, the 16-host capability matrix, and the degrade chain.
- Runs and operations Reading what Guild Stack wrote under .guild/, status and the dashboard, ops runbooks behind safety rails, initiatives, workspaces, the full event trace, and behavioral run analysis.