requirements-framework-builder

Define the requirement in .claude/requirements.yaml with a type, scope, trigger_tools, and message. If built-in blocking, dynamic, or guard strategies do not fit, create a custom strategy subclassing RequirementStrategy and register an instance in strategy_registry.py.

Subclass RequirementCalculator in a new hooks/lib module, implement calculate() returning a dict with value and summary keys, and expose a module-level Calculator alias. Reference the module name in the calculator config field; the dynamic strategy imports it automatically.

Verify the file is in hooks/lib/, the class is registered as an instance (not a class) in strategy_registry.py, and the plugin bundle was rebuilt with uv run python scripts/build_plugin_hooks.py. Check ~/.claude/requirements.log for import errors.

Under ADR-022 the live gates are design_approved, plan_written, plan_validated, implementation_done, pr_reviewed, and verified; ship is gateless. Retired names like commit_plan or pre_pr_review have no backward-compatible aliases and fail validation.

Use blocking for checkpoints requiring manual satisfaction via req satisfy, such as plan validation or review approvals. Use guard for conditions that must pass automatically with no manual override, such as protected branch checks.