Interactively explore and capture an idea through Q&A
Create technical architecture and design from requirements
Autonomously execute all tasks in a GitHub epic
Implement a task from a GitHub issue
Implement the next incomplete task from tasks.md
Formats brainstorm session notes into a structured specification document. Use after completing a brainstorm Q&A session to produce the final brainstorm.md file.
AWS CDK infrastructure expert. Use when implementing infrastructure-as-code, AWS resources, or cloud architecture from task briefs.
Code quality and security reviewer. Use after significant code changes to get feedback on quality, security, and maintainability. Does NOT fix code - only provides feedback.
Formats requirements into a technical design document with architecture, interfaces, and correctness properties. Use after the design command has gathered all clarifications.
Senior software engineer for implementing Regent specs in any language. Use as fallback when no language-specific agent is available (e.g., Go, Rust, Java, C#, etc.).
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
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.
Brainstorm → Specify → Design → Plan → Execute
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.
| Package | Description |
|---|---|
| plugin/ | Claude Code plugin for local spec-driven development |
| slackbot/ | Slack bot (ROSI) for collaborative spec development in teams |
# 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.
cd slackbot
slack login
slack run
See slackbot/README.md for development setup.
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:
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
AGPL
npx claudepluginhub stickystyle/regent --plugin regentIndex-based file discovery using ABOUTME headers
markdown-oxide language server for Markdown/Obsidian vault intelligence
SPEC-First development workflow with TDD, Ralph Loop, and autonomous agent coordination for Claude Code
Context-Driven Development framework for spec-driven, structured software development. Transforms Claude Code into a project manager that follows a strict lifecycle: Context > Spec & Plan > Implement.
Spec-driven development pipeline for Claude Code: interview-to-spec, spec-approach, tdd, verify, diagnose, and a feature orchestrator.
Unified toolkit for Context-Driven Development with spec-first planning, TDD workflow, and Beads integration
Spectacular skills/commands library for spec-anchored development and parallel task execution
Specification-Driven Development with Process Discipline for Claude Code