Design docs before code. Structured deliberation. Zero infrastructure.
From zero to a structured, multi-agent development workflow in minutes.
Interactive onboarding. Sets up structured spec-first workflows.
Explores your codebase. Enriches CLAUDE.md with real context, conventions, and patterns.
Multiple perspectives evaluate your idea independently. A design doc captures the decision before code is written.
Every feature starts with structured deliberation. Code comes after the design doc.
Agents are the implementation layer. Each has a single responsibility and follows the project conventions defined in your CLAUDE.md.
Evaluates ideas and gives strategic direction. First gate before any work begins.
Converts ideas into concrete tasks with acceptance criteria and clear scope.
Defines technical approach, architecture, and implementation direction.
Implements features following project conventions, writes tests, makes atomic commits.
Reviews code quality, patterns, and tech debt. Guards the standards of the guild.
Testing, edge cases, and regression. Validates that the implementation meets acceptance criteria.
Diagnosis and bug resolution. Isolates root causes and applies targeted fixes.
Schema changes and safe migrations. Handles rollback strategies and data integrity.
Resolves Claude Code integration issues, worktree configs, and environment problems.
Every feature starts with a design doc. Requirements, trade-offs, and decisions are captured before a single line of code is written.
Multiple agents analyze your idea independently, in parallel. Diverse perspectives converge into a clear, well-reasoned decision.
Design docs are tracked in git. Every decision has a rationale, every trade-off is documented. Context survives across sessions.
No servers, no databases, no API keys. Just markdown files and Claude Code. Works in any project, any language, any stack.