name: epic-story-orchestrator-zh description: Use when planning, extending, or drafting a Chinese long-form, world-heavy story or lore bible that needs reusable world rules, character registries, timeline control, chapter cards, consistency checks, and repo-tracked writeback. allowed-tools:
- Read
- Write
- Edit
- Bash(git diff --check)
- Bash(./scripts/doc-governance-check.sh)
- Bash(./scripts/pm/lint.sh)
- Bash(python3 .agents/skills/epic-story-orchestrator-zh/tests/validate_writeback.py)
- Bash(bash .agents/skills/epic-story-orchestrator-zh/tests/run_smoke.sh)
- Bash(rg:*)
license: MIT
metadata:
language: zh-CN
domain:
- longform-fiction
- worldbuilding
- lore task_modes:
- scaffold
- extend
- brainstorm
- chapter-card
- draft-scene
- polish
- audit
inputs:
required:
- story_slug
- task_mode
- premise
- canon_scope optional:
- target_length
- pov_mode
- style_constraints
- taboo_list
- existing_refs
- chapter_targets outputs:
- world-bible.md
- character-registry.md
- timeline.md
- plot-branches.md
- gameplay-canon-binding.md
- chapter-cards/*.md
- drafts/*.md
- consistency-report.md
- canon-log.md
writeback:
root: doc/game/lore/
/ append_only: - canon-log.md
- .pm/tasks/
.execution.md permissions: no_delete: true require_explicit_confirmation_for: - overwrite human-authored canon paragraphs
- large-scale retcon
- moving or deleting canon files
Epic Story Orchestrator ZH
Mission
Build and maintain a single canonical narrative truth for Chinese long-form stories in oasis7.
This skill orchestrates durable assets first, then prose slices. It never treats chat-only output as final truth.
When to Use
Use this skill when:
- the user wants to create or extend a Chinese long-form, world-heavy story, lore bible, or macro background narrative
- the work needs reusable world rules, character registries, timeline control, chapter cards, or canon tracking
- the task should produce repo-tracked story truth instead of chat-only prose
- the story must stay consistent across many chapters, volumes, or parallel arcs
Do not use this skill when:
- the user only wants a short blurb, slogan, marketing copy, or one-paragraph synopsis
- the request is really a product/design spec better owned by
prd.md,project.md, orgame-architect - the task is only polishing an existing Chinese paragraph and does not need story structure or writeback
- the output should remain temporary and must not become repo truth
Output Contract (must always be explicit)
For each run, return all three blocks:
- Artifacts changed
- exact repo paths
- operation (
create/update/append)
- Traceability map
- chapter cards ->
WR-*,CHAR-*,TL-*,PB-*,PRD-GAME-* - every current-game lore slice must answer
player_leverage,world_change_due_to_player, andcontrol_feeling_guarantee
- chapter cards ->
- Risk & next action
- blocker (
noneif absent) - next recommended step
- blocker (
Task Modes
scaffold: create a new story space from premiseextend: add or revise canon while preserving prior truthbrainstorm: produce 2–3 plot directions with one recommendationchapter-card: create chapter/scene cards from existing canondraft-scene: draft a scene or chapter slice from approved cardspolish: rewrite prose while preserving canon and toneaudit: inspect canon drift, retcon impact, and missing references
Canon Root
Default canonical root:
doc/game/lore/<story-slug>/
Recommended artifact layout:
world-bible.mdcharacter-registry.mdtimeline.mdplot-branches.mdgameplay-canon-binding.mdchapter-cards/drafts/consistency-report.mdcanon-log.md
Use stable IDs everywhere:
- world rules:
WR-* - factions:
FAC-* - locations:
LOC-* - technologies:
TEC-* - characters:
CHAR-* - timeline events:
TL-* - plot beats:
PB-* - chapter cards:
CH-*
Oasis7 Gameplay Canon Binding
For oasis7 current-game background story work, this skill is a lore asset authoring layer, not a standalone fiction pipeline.
Before creating or extending lore, bind the story space to current game truth:
PRD-GAME-012: 10-minute trust gate and first capability boundaryPRD-GAME-013: centimeter physical scale and indirect-control boundaryPRD-GAME-014: indirect-control control-feeling guaranteesPRD-GAME-015: mature-world small-player lane andplayer leverage != world activity- current claim envelope:
limited playable technical preview, unless formal game docs say otherwise
Required current-game lore fields:
gameplay_prd_refs: one or morePRD-GAME-*player_leverage: what new leverage the player gainsworld_change_due_to_player: what changed because of the player, not ambient world activitycontrol_feeling_guarantee: which accepted-intent / causality / fallback / reprioritize / resume guarantee the beat supportssmall_player_lane_stage:none,local_operator,regional_specialist, orlimited_scope_regional_influencerelease_claim_boundary: must not upgrade stage or marketing claims by implication
If a proposed lore beat cannot name the gameplay PRD refs and player leverage, keep it as brainstorm material and do not write it as canon.
One-Pass Perfect Workflow
0) Intake Gate
Collect the minimal context: story_slug, task_mode, premise, canon_scope.
If any required field is missing, stop and request it.
1) Route Gate
- If premise is ambiguous: run
brainstormfirst (2–3 options + 1 recommendation). - If premise is clear: continue.
2) Canon Gate (strict order)
world-bible.mdcharacter-registry.mdtimeline.mdgameplay-canon-binding.mdfor current-game lore
Do not produce chapter cards or prose that rely on undefined canon.
For current-game lore, do not produce chapter cards or prose that are not bound to PRD-GAME-* gameplay truth.
3) Plot Gate
Update plot-branches.md for major arc choices and append decision rationale to canon-log.md.
4) Card Gate
Create chapter cards before prose. Every card must cite at least one TL-* and one CHAR-*.
For oasis7 current-game lore, every card must also cite at least one PRD-GAME-* and include player_leverage, world_change_due_to_player, and release_claim_boundary.
5) Draft Gate
Draft prose in slices:
- scene slice: 800–2000 Chinese characters
- chapter slice: 2000–6000 Chinese characters
6) Polish Gate
Optionally apply humanizer-zh for Chinese tone quality while preserving canon facts.
7) Audit Gate
Update consistency-report.md and canon-log.md.
Verify timeline consistency, character-state consistency, and term drift.
8) Formal Writeback Gate
If bound to .pm task, append execution note to .pm/tasks/<TASK-UID>.execution.md with:
- Action
- Validation Command
- Expected Result
- Actual Result
- Blocker
- Next Action
Integration with Existing Local Surfaces
- governance entrypoint:
.agents/skills/README.md - skill authoring:
.agents/skills/writing-repo-owned-skills/SKILL.md - world/system decomposition:
.agents/skills/game-architect/SKILL.md - option comparison:
.agents/skills/bounded-brainstorming/SKILL.md - prose polish:
.agents/skills/humanizer-zh/SKILL.md
This skill does not replace bootstrap/router/verification/closeout workflow surfaces.
Supporting Files
templates/world-bible.template.mdtemplates/character-registry.template.mdtemplates/timeline.template.mdtemplates/plot-branches.template.mdtemplates/gameplay-canon-binding.template.mdtemplates/chapter-card.template.mdtemplates/canon-log.template.mdtemplates/consistency-report.template.md
Guardrails
- Do not create a second planning system outside repo truth.
- Do not overwrite existing canon silently.
- Do not delete canon files.
- Do not imitate a living author’s distinctive signature voice as a target.
- Do not output giant prose dumps before card-level planning.
- Do not write lore that contradicts current gameplay contracts or turns ambient world activity into player leverage.
- Do not use lore to imply
closed beta,play now, direct first-person control, global governance power, or broader launch readiness unless those claims already exist in current repo truth. - Keep default output language in Chinese unless explicitly requested otherwise.
Verification
Run checks before claiming ready:
git diff --check./scripts/doc-governance-check.shpython3 .agents/skills/epic-story-orchestrator-zh/tests/validate_writeback.pybash .agents/skills/epic-story-orchestrator-zh/tests/run_smoke.sh
For story assets, run reference scan:
rg -n 'WR-|FAC-|LOC-|TEC-|CHAR-|TL-|PB-|CH-' doc/game/lore/<story-slug>/
For current-game lore, also scan gameplay binding:
rg -n 'PRD-GAME-012|PRD-GAME-013|PRD-GAME-014|PRD-GAME-015|player_leverage|world_change_due_to_player|release_claim_boundary' doc/game/lore/<story-slug>/