What problem does it solve? When a stock-docs document becomes obsolete, its derived knowledge topics, index entries, and routing rules in the .Knowledge base linger as stale references that mislead AI coding agents. This Skill removes the document's topics and cleans every dependent mapping so the knowledge base stays consistent. ## Core Features & Use Cases - Topic Deletion by Document: Accepts a .Knowledge/stock-docs file path or filename fragment, matches related topics via .Knowledge/index.md, and deletes the corresponding topic files. - Routing Manifest Cleanup: Removes stale topicPaths, taskToTopicRules, topicDependencies, and topicMetadata entries from manifest-routing.json and matcher files, and reassigns fallbackTopic when it is deleted. - Ambiguity Safety: When a filename fragment matches multiple topics, it asks the user to confirm the deletion scope before removing anything. - Use Case: After deprecating a design document, run this Skill to delete its two derived topics, clean the routing manifest, and receive a summary of deleted topics, index entries removed, and manifest fields adjusted. ## Quick Start Ask the agent to delete the project context for a specific stock-docs document by giving its filename or a matching fragment, for example: remove the knowledge topics for the callback document.
