What problem does it solve? Once a knowledge-graph ontology is designed, teams still face the hard part: turning that schema into a working codegen tool without guessing at build order, markers, or project conventions. This Skill converts a confirmed ontology into a phased, verifiable implementation roadmap, deriving phase order from the ontology's relationship triples and discovering markers against real code. ## Core Features & Use Cases - Phase derivation from ontology triples: Topologically sorts the ontology's relationship triples to produce a build order, presented as a draft for human confirmation. - Marker discovery against real code: Reads actual source code to find markers, since the ontology is pure schema and contains none. - Multiple output modes: Emits an artifact pair, an unattended handoff prompt for an autonomous agent, or implements phase by phase in the current session. - Use Case: After designing a Neo4j knowledge-graph ontology for a .NET codebase, supply the ontology file and receive a phased plan where each phase is implemented and independently validated before the next begins. ## Quick Start Ask the assistant to plan the knowledge-graph codegen implementation using the confirmed ontology file at a path you provide.