Dominik Rehse Stdd
dominik-rehse-stdd is a Claude Code plugin for the Ship phase that enforces spec-first, one-test-at-a-time test-driven development through commands and guards.
by dominik-rehse · github.com/dominik-rehse/stdd
Install to keep Claude Code on spec-first and one-test-at-a-time TDD rails with slash commands and pre-commit guards.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install dominik-rehse-stdd@dominik-rehse/stddBuilt 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:dominik-rehse/stdd") and the paste-ready config with skillselion.get_install_config("plugin:dominik-rehse/stdd").
What it does
dominik-rehse-stdd is a Claude Code plugin bundle aimed at solo builders and small teams who want spec-driven and test-driven development to stick inside agent sessions, not only in human-run terminals. It packages slash commands and guard-style hooks (including precommit and pretooluse patterns suggested by its keywords) so Claude is nudged to write or honor a spec before coding, advance tests one at a time, and respect checkpoints before risky tool use. That matters when fast agent loops otherwise skip failing tests or bulk-implement features. The plugin fits backends, CLIs, and SaaS codebases where regressions are expensive. It is process-oriented rather than a single API integration: you install it when you already believe in TDD and need mechanical enforcement in Claude Code. Complexity is intermediate because you must understand red-green-refactor and your own test runner setup. Confidence is moderate given limited public SKILL detail beyond repository metadata and keyword hints.
Highlights
- Slash commands for spec-first and STDD workflows in Claude Code
- One-test-at-a-time discipline with dedicated command keywords
- Pre-commit and pre-tool-use guards that enforce process before edits
- Spec-first framing so implementation follows agreed behavior
- Community plugin bundle with a single packaged plugin entry
Why builders use it
Agent-assisted coding often jumps straight to implementation and skips specs, ordering, and failing tests you actually run.
After you register the plugin, sessions gain repeatable STDD commands and guard hooks so work stays spec-first and test-led through commit and review.
At a glance
- Type - Plugin in Testing.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is dominik-rehse-stdd for?
Solo and small-team developers who already practice or want strict spec-first TDD inside Claude Code sessions.
When should I use dominik-rehse-stdd?
Use it when starting or continuing feature work where you want specs written first, tests added one at a time, and guards before commits or risky tool use.
How do I add dominik-rehse-stdd to my agent?
Install the dominik-rehse/stdd Claude Code plugin from the community catalog, enable it in your Claude Code plugins config, then invoke its slash commands and hooks in your project workspace.
Comments
Share how you use dominik-rehse-stdd, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.