story-bible

Files (3)

• SKILL.md
• openai.yaml · agents/
• structure.md · references/

SKILL.md (first lines)

# Story bible

Maintain the author's internal fiction wiki in the chosen destination. Use the existing organization when it supports the task. For a new story bible, follow [the default structure and entry patterns](references/structure.md), creating only sections supported by the available material. Keep each fact's primary home clear, and link related entries rather than maintaining duplicate accounts.

Before reading, recording, or reviewing fiction, read and follow [the editorial contract](../references/editorial-contract.md).

## Ground rules

- Give each claim the narrowest applicable status. Status belongs to individual claims; never assign one status to a whole character, place, scene, or page.
  - **Established:** Reliably established by the manuscript.
  - **Author decision:** Confirmed privately by the author, whether or not the manuscript reveals it.
  - **Planned:** Intended but still changeable.
  - **Possibility:** An option under consideration.
  - **Inference:** A reading supported by the text but not confirmed.
  - **Superseded:** Retained for history but no longer current.
  - **Needs reassessment:** Previously supported, but its supporting evidence is no longer current. Preserve the former evidence; do not present the claim as currently established or disproved.
  - **Conflict:** Two sources or claims require resolution. Preserve both until the author resolves them.
- Record attributed statements separately from the propositions they assert when needed, following the editorial contract.
- Record enough provenance to find the evidence again. For manuscript facts, identify the draft or version, stable location, and shortest useful passage. Record a revision date when available; do not invent a version or infer authority from recency alone. For private decisions, identify the author source and date or conversation context.
- Use the author's chosen wiki as the system of record. Manuscript sources may live elsewhere. Do not create a parallel wiki or synchronization layer unless requested.

## Choose the operation

### Build

Read the requested source material within the stated scope. Inspect the chosen destination before creating anything. Organize claims where the author will look for them, reusing existing entries and conventions. Include private decisions, plans, and possibilities when in scope, with their author sources and statuses.

Read [the structure reference](references/structure.md) before creating or organizing entries. Adapt its sections to the destination and the amount of material. Preserve existing paths, page organization, and unrelated page properties; propose any needed migration separately. Keep drafts and editorial feedback in their chosen locations and link to them where useful.

Record only source-backed claims. Keep these distinctions explicit wherever they matter:

- what happens in world chronology and when the narrative reveals it;
- what is true in the world and what each character knows at a given point;
- source-universe canon, story canon, and deliberate departures between them.

Link related claims when that improves retrieval. Do not fill empty categories or invent details for completeness.

### Update or reconcile

Read the existing wiki entries and their cited sources before editing. Change the narrowest affected claims. Add new provenance rather than replacing useful evidence.

Honor explicit replacement relationships between drafts. If the author designates draft 2 as replacing draft 1 and a coat changes from red to blue, update the current claim and mark the replaced claim Superseded with its original evidence. A later timestamp alone does not make a draft authoritative.

If a revision removes a claim's only support, mark it Needs reassessment and identify the lost support. Do not continue presenting it as currently established or assume its opposite is true. Preserve independently confirmed author decisions.

Reserve Conflict for incompatible simultaneously current sources or unclear revision intent. Preserve both claims and ask for resolution rather than choosing by preference. When resolved, record the decision and retain superseded evidence as history.

### Retrieve

Answer from the current chosen wiki and cited source material. State claim status and provenance close to the answer. Separate established facts and author decisions from plans, possibilities, inferences, superseded ideas, claims needing reassessment, and unresolved conflicts. Say when the wiki does not support an answer.

### Assemble a context packet

Build the smallest packet that supports the stated task. Include its purpose, source scope, spoiler boundary, relevant claims with statuses and provenance, event versus reveal order, character knowledge at the relevant point, applicable canon departures, and unresolved conflicts. Omit unrelated lore and private decisions outside the requested working scope.

## Verify changes

After a write, read back every changed entry in the chosen destination. Check claim status, provenance, chronology versus reveal order, character knowledge, and canon scope where applicable. Report what changed and any claim, conflict, or source location that could not be verified.

Check that new entries are reachable from the bible's home or a section index, internal links resolve, and repeated summaries point to the claim's primary home. Remove empty placeholders created during the operation; preserve the author's existing material.

From atrnh/skills, MIT.

More from atrnh/skills