What problem does it solve? Planning and implementing a feature without knowing the existing codebase leads to duplicated modules, broken dependencies, and parallel tasks colliding on shared files. This Skill queries a graphify dependency graph to produce a compact grounding document so Spec Kit commands plan against real code structure instead of re-exploring the repo from scratch. ## Core Features & Use Cases - Graph-grounded context generation: Runs graphify explain, query, and path commands against graphify-out/graph.json to map feature anchors to real files and symbols. - Blast radius and collision detection: Reports per-anchor dependencies and flags shared/mutable files (route manifests, barrels, registries) that must be serialized during parallel implementation. - Repo or merged-stack scope: Supports single-repo graphs or a merged cross-repo stack graph for features spanning frontend and backend. - Use Case: Before running /speckit-plan on a new tournament feature, invoke this Skill to write graphify-context.md listing the existing modules it touches, which files depend on them, and which shared files constrain parallel task waves. ## Quick Start Ask the assistant to generate the graphify context file for the current feature, optionally passing a feature directory or the word merged for the cross-repo stack graph.
