Stickystyle Regent
stickystyle-regent is a Claude Code plugin for the Build phase that implements a spec-driven development workflow with TDD alignment for Claude Code sessions.
by stickystyle · github.com/stickystyle/regent
Run spec-driven development and TDD-oriented workflow inside Claude Code so features start from specs, not ad-hoc prompts.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install stickystyle-regent@stickystyle/regentBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:stickystyle/regent") and the paste-ready config with skillselion.get_install_config("plugin:stickystyle/regent").
What it does
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 solo builders, 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.
Highlights
- 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
Why builders use it
Solo builders lose days when Claude Code jumps straight to code from vague prompts and the feature scope drifts away from what they actually needed to ship.
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.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is stickystyle-regent for?
Solo builders 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.
Comments
Share how you use stickystyle-regent, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.