regent

Regent

The architect who listens to your team argue, writes down what matters, and hands developers a crystal-clear blueprint.

Regent turns vague ideas into production-ready code through structured brainstorming. Instead of jumping straight to implementation, Regent asks the right questions—one at a time—to build a complete spec before anyone writes a line of code.

How It Works

Brainstorm → Specify → Design → Plan → Execute

1. Brainstorm — An AI asks probing questions about your feature, learning your codebase as it goes
2. Specify — Answers become formal EARS-format requirements
3. Design — Architecture and correctness properties are generated
4. Plan — TDD-ordered tasks with test-first implementation
5. Execute — Each task becomes a focused PR with tests

Why It Matters

• Specs capture the why, not just the what
• Voice discussions don't disappear into the ether
• Junior devs get senior-quality specs to implement against
• Every feature starts with tests, ends with a PR

The Team Experience

Start a brainstorm in Slack with /brainstorm --huddle --repo acme/api. Regent spins up a voice call and listens while your team talks through the problem. When someone types @regent JWT for stateless auth, the bot already heard the debate about revocation tradeoffs—and asks smarter follow-up questions because of it.

Packages

Package	Description
plugin/	Claude Code plugin for local spec-driven development
slackbot/	Slack bot (ROSI) for collaborative spec development in teams

Quick Start

Claude Code Plugin (Solo Development)

# Add the marketplace
/plugin marketplace add stickystyle/regent

# Install the plugin
/plugin install regent@stickystyle-regent

# Initialize in your project
/regent:init

# Start brainstorming
/regent:brainstorm

For local development, add the local directory as a marketplace:

# Add local marketplace (run inside Claude Code)
/plugin marketplace add /path/to/regent

# Install from local marketplace
/plugin install regent@regent-plugins

See plugin/README.md for full documentation.

Slack Bot (Team Collaboration)

cd slackbot
slack login
slack run

See slackbot/README.md for development setup.

Dogfooding

We're building Regent using Regent. The Slack Bot Epic tracks the complete spec-driven development of ROSI—from brainstorm through implementation—all generated by the workflow itself.

This gives us:

• Real-world validation of the spec format
• A working example of what Regent produces
• Continuous feedback on the developer experience

Repository Structure

regent/
├── .claude-plugin/    # Plugin manifest
├── plugin/            # Claude Code plugin
│   ├── commands/      # Slash commands (/regent:brainstorm, etc.)
│   └── agents/        # Specialized agents (writers, validators)
└── slackbot/          # Slack ROSI app (Deno/TypeScript)
    ├── functions/     # Custom Slack functions
    ├── workflows/     # Workflow definitions
    └── triggers/      # Trigger configurations

License

AGPL