Guild

Guild

Claude Code plugin

Self-evolving specialist agent teams that plan carefully, execute autonomously, and preserve project memory over time.

Get started Read the docs

Quick start

Install, run, approve the plan

Guild becomes autonomous after the planning contract is approved. The first few minutes are where it asks the important questions.

1

Install the plugin

claude plugin marketplace add lookatitude/guild
claude plugin marketplace update guild
claude plugin install guild@guild --scope project
# Restart Claude Code before running /guild
2

Start with a real outcome

/guild Add usage-based billing, verify it, and write the release notes.
3

Use teams only when needed

export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

System shape

Planning discipline, specialist execution, durable memory

Question-driven planning

Goals, constraints, acceptance tests, non-goals, risk, and autonomy boundaries are captured before execution starts.

Specialist teams

13 agents compose per task instead of all firing at once.

Context bundles

Each specialist gets a compact authoritative brief instead of a project-wide context dump.

Project memory

Raw sources, decisions, standards, product notes, concepts, and source summaries live in .guild/.

Evidence gates

Review and verification consume handoff receipts with changed files, assumptions, tests, citations, and risks.

Self-evolution

Skills and specialists evolve through reflections, shadow mode, flip reports, and versioned rollback.

Small static site

Organized for growth without a framework

The site is intentionally just a few public pages, generated by a dependency-free Node script. The reference page is rebuilt from the real plugin files.

Docs

Guild operating guide

Install, lifecycle, specialists, context assembly, wiki memory, evolution gates, and runtime state.

 Reference

Commands, agents, skills

7 commands, 13 agents, and 72 skills mapped from the repo.

 Use case

URL shortener E2E run

The plan, what each agent actually did, final artifacts, tests, and reflection signal.

How it works

The Guild system

Guild gathers intent, selects the smallest useful team, assembles focused context, records durable memory, and evolves only when evidence proves the change belongs.

System map

Architecture with clear ownership

The architecture map shows the boundary between the installed plugin, execution backends, specialist roster, and durable project state.

  • Commands orchestrate work without hiding state.
  • .guild/ keeps plans, memory, runs, and evolution auditable.