Claude Code is powerful but chaotic.
Guild gives it structure.
9 specialized agents. 10 skill workflows. One command.
npx guild-agents init
click to copy
Three steps to forge your guild
Interactive onboarding. Generates 9 agents and 10 skills, calibrated to your project.
Explores your codebase. Enriches CLAUDE.md with real context so every agent understands your project.
Full pipeline: evaluate, spec, implement, review, QA. One command triggers the whole guild.
How /build-feature orchestrates your guild
Nine specialists. Each one knows their role.
Evaluates ideas and gives strategic direction. The first voice heard before any quest begins.
Converts ideas into concrete tasks with clear acceptance criteria. The bridge between vision and work.
Defines technical approach and architecture. Plans the route so others can march with purpose.
Implements code following project conventions. Test-driven, disciplined, and precise in every commit.
Reviews quality, patterns, and technical debt. Nothing ships without the Scout's keen eye.
Testing, edge cases, and regression. Hunts bugs before they reach the wild.
Diagnosis and bug resolution. When something breaks, the Tracker follows the trail to the root cause.
Schema changes and safe migrations. Handles the arcane art of evolving data without destruction.
Resolves Claude Code integration issues. Navigates the terrain where your tools meet the platform.
Why structure beats chaos
Claude Code can do anything — which means it often does everything at once. Guild channels that power through specialized agents who each know their boundaries.
Agents define identity and expertise. Skills define workflow and process. Clean separation, infinite composability. No framework lock-in, just plain Markdown.
Every session reads CLAUDE.md, PROJECT.md, and SESSION.md. Context survives across sessions, branches, and team members.
No servers. No APIs. No tokens to manage. Just Markdown files and Claude Code. Run guild init and you are ready. It works wherever Claude Code works.