Graphify Novel

graphify-novel: Writing assistant with knowledge graph

[English](README.md) | [Tiếng Việt](README.vi.md)

Write. Don't track.

As your story grows, so does the overhead. Where was this character last seen, did you already establish that rule, which threads are still open? ```graphify-novel``` handles all of that so you can stay in the prose.

Give it a premise and it scaffolds your story bible. Feed it a chapter and it checks for contradictions, flags unresolved setups, and updates every character and thread automatically. Ask it a question and it traces connections across your full manuscript.

This skill uses [graphify](https://github.com/safishamsi/graphify) under the hood to extract a knowledge graph from your chapters and bible, mapping relationships between characters, locations, events, and themes across the full manuscript. This is what powers cross-chapter queries, structural hub detection, and the implicit connection hints in review.

---

Prerequisites

• Any coding assistant (Copilot, Claude, etc)

• [graphify](https://github.com/safishamsi/graphify) skill installed. If not already installed, the assistant will help you install it before continuing.

---

Installation

npx skills add Anshler/graphify-novel

---

Project structure

/
  chapters/          ← manuscript files (preferably .txt or .md)
  draft/             ← work-in-progress (excluded from graph)
  static/            ← static files, images, etc (excluded from graph)
  bible/
    premise.md
    timeline.md
    characters/
    threads/
    world/
  graphify-out/      ← generated knowledge graph
  .graphifyignore

You can start with an empty project. But if it's an existing project, make sure your finished chapters are in `chapters/`, in-progress drafts are in `draft/` and static files in `static/`.

If you already had an existing bible/story-tracking structure, it won't be compatible. Move them outside the project then retrofit them into the new stru