Turn one big GDD into many docs with smart import
Smart import takes a single sprawling design document and proposes a clean split into separate, structured docs you review before anything is created. Here is how it works.
Smart import takes one large source — a sprawling GDD, a pasted brain dump, a doc at a URL — and proposes carving it into several separate, structured documents. Nothing is created until you review the proposal and choose what to keep. It is the fastest way to move an existing design from a single wall of text into a Gameframe vault.
What can you import?
Smart import accepts a source three ways:
- Upload — a file from your machine.
- Paste — drop the raw text straight into the modal.
- URL — point it at a document on the web.
Whichever route you use, the committed documents come out as clean Markdown, ready to edit in the Gameframe editor.
How does the split actually happen?
Smart import runs in three steps: analyze, review, commit.
- Analyze — you supply the source and Gameframe stages it, then asks a model to propose a split. This step writes nothing to your documents. You poll until the proposal is ready.
- Review — the proposal lists each document the model would carve out, with a title, a semantic label (for example “Boss Design”), and a few extracted facts shown as chips (“3 phases”, “12 stats”). You toggle which ones to keep.
- Commit — only the documents you selected are created as real docs with a first version each, on the vault.
What does the review step show you?
For every proposed document you see its title, a free-text kind label, and short extracted entities so you can tell at a glance whether the split makes sense. If the model could not find a confident split, the proposal comes back empty and tells you so — it does not invent structure that is not there.
Where do the new documents land?
The selected documents are created on the vault’s main branch, each with its own version-one. If the model suggests a branch name for a document, that suggestion is shown for context only in this version — the docs are committed to main, and you branch from there as normal.
Why review before committing?
Because an automated split is a proposal, not a decision. You see every document the model wants to create, you keep the ones that are right, and you drop the rest before a single doc exists in your vault. The model proposes; you commit.
What should you import first?
Start with the messiest document you have — the one GDD that has grown into a dozen sections nobody wants to untangle by hand. Smart import is at its best when the source is exactly the sprawl you have been avoiding.
