Retract a Foundation SoftwareFeature and dependent UserStories from the graph.
npx skills add https://github.com/danielterra/FOUNDATION --skill feature-remove
Please help me install this Agent Skill. Skill: feature-remove Source: https://github.com/danielterra/FOUNDATION/tree/main/.claude/skills/feature-remove Command: npx skills add https://github.com/danielterra/FOUNDATION --skill feature-remove
This Skill removes a Foundation SoftwareFeature and its dependent UserStories from the knowledge graph, addressing the need to retire obsolete software features without leaving orphaned references.
Confirm the Feature IRI and execute the sequenced retract to remove the feature and its UserStories from the graph.
High-intent search queries and answers about installing and using this skill.
To retract a software feature safely, you must analyze the graph dependencies and report all backlinks before deletion. A sequenced retract workflow enforces referential integrity by identifying dependent UserStories and requires explicit confirmation before permanent destruction.
Dependent UserStories are permanently removed alongside the Foundation SoftwareFeature during the retract workflow. The process executes a sequenced deletion that targets both the feature and its associated UserStories to maintain referential integrity across the knowledge graph.
Yes, you can check backlinks and related metadata before deletion. The retract workflow analyzes all dependencies and reports every backlink connected to the SoftwareFeature, ensuring you have full visibility into the impact before proceeding with permanent removal.
The best way to retire obsolete features without permanent deletion is to mark the SoftwareFeature as Cancelled rather than executing a full retract. This provides a rollback-safe path that preserves the feature and its UserStories in the graph for future reference.
Removing a feature requires explicit user confirmation because the retract process permanently destroys the SoftwareFeature and its dependent UserStories. This safeguard ensures that irreversible graph modifications only proceed after an operator reviews all reported backlinks and dependency impacts.
Yes, the sequenced retract workflow includes error reporting to maintain referential integrity during deletion. If any issues occur while removing the SoftwareFeature and its UserStories from the graph, the workflow reports the errors to prevent silent data corruption.
oakossDesign ontologies and select graph databases for knowledge graph implementation.
Pupfish-LLCIdentify data quality issues in loaded Qlik datasets and generate a validation report.
mitchuskiMap entities and relationships across the 0xagentprivacy ecosystem.
danielterraOrchestrate end-to-end FOUNDATION SoftwareFeature planning by coordinating child UserStories via /userstory-plan.
