capability-wiring-gap-documentation-is-not-activation
New skills, agents, and MCPs that are installed and documented but not explicitly wired into protocol phase tables are effectively orphaned — they will never be invoked because no phase references them. Every new capability requires three wiring steps: (a) add to protocols.md Phase 0 specialist patterns table with dispatch timing, (b) add invocation to the relevant execution phase (e.g., Phase 3.5 for code quality tools), and (c) update MEMORY.md or hooks-registry.md with behavioral enforcement. A capability only exists if a protocol step triggers it.
Related
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- docker
- capability-activation-gap-new-skillsagents-must-be-wired-int
- oracle
- openclaw
- security-reminder-hook-blocks-literal-exec-eval-in-prose
- lint-orchestrators-list-requires-explicit-update-after-skill
setup-curator-guard-stays-advisory-during-pre-approved-batch(archived)- runwal-bkc-website-is-hobby-not-official-production
- helios-helix-integration-feature-flagged
- phantom-hooks-referenced-but-not-registered
- helix-phantom-hooks-startup-brainstorming-gates