harness-setup

To enforce mandatory workflow phases in Claude Code, you need a mechanical harness that blocks completion until specs, tests, and doc updates are satisfied. This setup generates hook scripts and slash commands to automate quality gates.

Stopping Claude from skipping doc updates during autonomous runs requires mechanical enforcement via git hooks and a state machine. The system blocks task completion until verification phases are explicitly satisfied, preventing silent skips.

Yes, scope-aware quality gates can be applied by inferring whether work is a feature, patch, or design change. The enforcement harness then triggers only the required workflow phases specific to that scope.

Bootstrapping living documentation involves scaffolding docs templates and filling missing PRD, system-design, and component-registry specs based on the codebase. This ensures documentation stays current alongside code changes.

Yes, the superpowers dependency is required to set up this Claude Code workflow enforcement. It provides the foundational capabilities needed to wire enforcement through settings and hook scripts.

If a Stop-hook blocks the chat in an infinite loop during autonomous execution, built-in loop detection safety guardrails intervene. These guardrails prevent the enforcement mechanism from trapping the chat in a block and reply cycle.