Stickystyle Regent
- Updated January 2, 2026
- stickystyle/regent
stickystyle-regent is a Claude Code plugin that implements a spec-driven development workflow with TDD alignment for Claude Code sessions.
About
stickystyle-regent is a one-plugin Claude Code workflow from stickystyle/regent that pushes spec-driven development: you define behavior and acceptance intent first, then let the agent implement against that contract with TDD called out in the taxonomy keywords. For developers, it counters scope creep from vague prompts by making the spec the source of truth Regent and Claude iterate on. It spans Validate when you narrow what to build and Build when you execute, with natural handoff to Ship testing when specs encode examples. It is a process plugin, not a deploy or SEO tool—install when you want a named Regent ritual inside Claude Code rather than inventing your own planning doc chain each sprint.
- Single-plugin Regent bundle for spec-driven development on Claude Code
- Workflow keywords tie spec-driven delivery to TDD practices
- Positions Claude as executor under written specs rather than improvising scope
- Community-listed development workflow from stickystyle/regent
- Useful when solo builders need repeatable structure across features
Stickystyle Regent by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install stickystyle-regent@stickystyle/regentAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| Last updated | January 2, 2026 |
|---|---|
| Repository | stickystyle/regent ↗ |
What it does
Run spec-driven development and TDD-oriented workflow inside Claude Code so features start from specs, not ad-hoc prompts.
Who is it for?
Best when you're shipping SaaS or APIs and want structured spec-driven plus TDD habits without maintaining a custom Superpowers-style doc stack.
Skip if: Quick one-file experiments where a formal spec is overhead, or teams that already enforce specs entirely outside Claude in Jira or Notion only.
What you get
After you add Regent, Claude Code sessions follow a spec-first workflow so implementation and tests trace back to an agreed spec instead of one-off agent guesses.
- Regent spec-driven workflow available inside Claude Code
- Feature work anchored to specs rather than prompt-only sessions
- Clearer path from scope to tested implementation for solo shipping
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
Spec-driven workflow plugin, not an MCP integration or a single lint-or-format task skill.
FAQ
Who is Stickystyle Regent for?
Developers and small teams using Claude Code who want spec-driven development and TDD-oriented discipline baked into the agent workflow.
When should I use Stickystyle Regent?
Use it at the start of a feature or epic when you need a spec before implementation and want Claude to follow Regent’s workflow instead of free-form coding.
How do I add Stickystyle Regent to my agent?
Install the Regent plugin from stickystyle/regent per repository instructions, register it in Claude Code, then invoke the spec-driven workflow when beginning new work.