What problem does it solve?
It reduces the risk and effort involved in extending an existing Claude Code harness, where changes must be coordinated across multiple files (state initialization, stop-gate requirements, scope evaluation, and command wiring) to avoid deadlocks and inconsistent enforcement.
Core Features & Use Cases
- Phase extension with consistency guardrails: Adds new enforcement phases to the harness state machine and ensures the phase name is updated everywhere it is checked and marked.
- Scope addition with correct inference ordering: Introduces new scopes, including the file-pattern trigger and REQUIRED phase mapping, while maintaining the stop gate’s top-to-bottom specificity order.
- Hook and command expansion: Adds new hook scripts (SessionStart, PreToolUse, PostToolUse, Stop) and/or slash commands, then updates wiring and harness documentation so the new enforcement behavior actually runs.
- Multi-file coordination checklist: Provides exhaustive update steps to modify all required harness touchpoints together rather than piecemeal.
Quick Start
Ask the skill to extend your harness by adding a new scope and required phases, then follow its checklist to update the stop gate, scope evaluation, tests/smoke logic, and harness documentation.
