Bens Claude Code Toolkit
Run structured discovery, EARS specs, implementation plans, and test strategy before coding a feature in Claude Code.
Overview
bens-claude-code-toolkit is a plugin marketplace for the Validate phase that packages think-discover-define for discovery-led specs, plans, and test strategy in Claude Code.
What is this marketplace?
- think-discover-define plugin: discovery Q&A then formal feature spec
- EARS-style requirements and explicit state contracts in the spec
- Derived implementation plan tied to the approved spec
- Test strategy artifact produced alongside the plan
- Spec-driven flow reduces rework before agent-assisted coding
- Marketplace bundles 1 plugin: think-discover-define v1.0.2
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders often let agents implement features before requirements and test expectations are explicit, which breeds rework and flaky acceptance criteria.
Who is it for?
Indie developers shipping agent-assisted features who want lightweight spec discipline without a full enterprise toolchain.
Skip if: Teams that already enforce formal PRDs in Jira or who only need ad-hoc one-off prompts without structured specs.
What do I get? / Deliverables
After registration you get a repeatable path from discovery questions to EARS spec, implementation plan, and test strategy ready to drive Claude Code builds.
- Formal feature spec with EARS requirements and state contracts
- Implementation plan aligned to the spec
- Test strategy document for the feature
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Canonical shelf is validate/scope because the toolkit starts with discovery questions and formal specs before implementation. think-discover-define turns vague ideas into scoped requirements and state contracts—the core validate/scope job for solo builders.
How it compares
Curated single-workflow marketplace, not a general MCP server or UI generator.
Common Questions / FAQ
Who is Bens Claude Code Toolkit for?
Claude Code users who want spec-driven feature work—discovery, EARS requirements, plans, and tests—in one registered plugin.
When should I use Bens Claude Code Toolkit?
Use it at the start of a new feature or significant change, before asking the agent to write production code or tests.
How do I add Bens Claude Code Toolkit to my agent?
Add the marketplace from owner benedekvarga in Claude Code plugin settings, install think-discover-define, then invoke it when scoping a feature.