planned-ghost-skills-must-be-removed-not-listed
Skills listed as PLANNED in a skill file but not yet created constitute ghost capability references that create a false capability map. Found in coherence-orchestrator: dependency-graph, spec-tracker, documentation-intelligence, changelog-coherence were listed as PLANNED but non-existent. Correct fix is removal and replacement with a distributed-ownership note, never leaving PLANNED stubs that make the system appear to have capabilities it lacks.
Related
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- oracle
- docker
- clawteam-openclaw-multi-agent-swarm-evaluation
- openclaw
- ghost-planned-skills-in-coherence-orchestrator-registry
- ghost-planned-skills-create-false-capability-claims
- ghost-planned-skill-refs-create-false-capability-assumptions
- dead-prose-pointers-accumulate-via-progressive-disclosure