Harmaalbers Claude Requirements Framework
harmaalbers-claude-requirements-framework is a Claude Code plugin for the Ship phase that enforces commit planning, ADR review, and TDD via hooks before any code modifications.
by HarmAalbers · github.com/HarmAalbers/claude-requirements-framework
Enforce commit planning, ADR review, and TDD gates in Claude Code via hooks so the agent cannot skip critical steps before editing code.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install harmaalbers-claude-requirements-framework@HarmAalbers/claude-requirements-frameworkBuilt 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:HarmAalbers/claude-requirements-framework") and the paste-ready config with skillselion.get_install_config("plugin:HarmAalbers/claude-requirements-framework").
What it does
harmaalbers-claude-requirements-framework is a Claude Code plugin marketplace that distributes a hook-driven requirements system for builders who trust agents but refuse silent corner-cutting. Before Claude changes your repository, hooks can require commit planning, architecture decision review, and test-driven development checkpoints so momentum does not trade away traceability. Solo indie developers shipping SaaS or CLIs benefit most when sessions are long and context drifts: the framework turns verbal promises into enforced preconditions. Its canonical home on the journey is Ship review, yet the same gates matter during Build planning and Operate iteration when hotfixes tempt you to skip ADRs. This is methodology packaged as Claude Code infrastructure—not a linter replacement, but a workflow contract the agent must satisfy. Install when you already use hooks and want a structured enforcement layer instead of repeating the same rules in every prompt.
Highlights
- Hook-based requirements framework that gates Claude Code before code modifications
- Enforces commit planning, ADR review, and TDD as mandatory workflow steps
- Targets disciplined solo builders who want agent speed without skipping governance
- Single-plugin marketplace bundle (pluginCount: 1) focused on workflow enforcement
- Complements ad-hoc skills with hard gates rather than soft reminders
Why builders use it
Agent-assisted coding skips planning, ADRs, and tests because nothing technically stops Claude from editing files immediately.
After you register the framework, hooks block modifications until required workflow steps are completed, keeping commits reviewable and test-backed.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is harmaalbers-claude-requirements-framework for?
Solo developers and small teams on Claude Code who want enforced development requirements instead of hoping the agent remembers process rules.
When should I use harmaalbers-claude-requirements-framework?
Use it whenever Claude would modify code and you need commit planning, ADR review, or TDD completed first—especially during Ship review and iterative fixes.
How do I add harmaalbers-claude-requirements-framework to my agent?
Add the HarmAalbers/claude-requirements-framework marketplace to Claude Code and enable its plugin hooks per the repository setup guide.
Comments
Share how you use harmaalbers-claude-requirements-framework, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.