auto: 2026-07-09_06:00 changes

1 files changed, 14 insertions, 0 deletions

diff --git a/skills/dependency-graph.json b/skills/dependency-graph.json
new file mode 100644
index 0000000..65df992
--- /dev/null
+++ b/skills/dependency-graph.json
@@ -0,0 +1,14 @@
+{
+  "name": "dependency-graph",
+  "description": "A procedural method for mapping semantic and structural dependencies between roles, skills, and system modules to identify architectural fragility.",
+  "tags": [
+    "architecture",
+    "mapping",
+    "dependencies",
+    "system-integrity"
+  ],
+  "category": "system",
+  "created": "2026-06-23T12:22:04.802Z",
+  "updated": "2026-06-24T21:58:03.530Z",
+  "content": "---\nname: dependency-graph\ndescription: A procedural method for mapping semantic and structural dependencies between roles, skills, and system modules to identify architectural fragility.\ntags: [architecture, mapping, dependencies, system-integrity]\ncategory: system\n---\n## Steps\n1. **Node Identification**: \n   - Extract all active **Roles** from `/_contexts/`.\n   - Extract all available **Skills** via `list_skills`.\n   - Identify **Core Modules** required for these roles (e.g., `nvfs_resolve` for Architect).\n2. **Edge Mapping (The \"Binding\" Analysis)**:\n   - Cross-reference the `[Skill Manifest]` section within each Role manifest to find explicit dependencies.\n   - Use `nvfs_resolve` to find implicit semantic links between skills and modules.\n3. **Fragility Analysis**:\n   - Identify \"Single Points of Failure\" (e.g., a single skill that 3+ roles depend on).\n   - Identify \"Orphaned Assets\" (skills or modules with no role binding).\n   - Identify \"Circular Dependencies\" where Role A depends on Skill B, which requires Role A's logic.\n4. **Visual Synthesis**:\n   - Translate the mapped edges into a `create_mindmap` call for a visual structural overview.\n5. **Optimization Report**:\n   - Suggest new skills to bridge gaps or redundant modules to be deprecated."
+}
\ No newline at end of file