of long-term serialization a ledger that remembers the stateIt owns a single master planning document file, and each time an episode is written, within it the episode status tableis updated. It is used with the same mechanism across both webtoon and web novel lines. It is the axis of the loop that appears twice: at the start of the chain (state establishment) and at the end (state update).
1. Why a ledger is needed
Long-term serialization is interrupted dozens of times by sessions. If you start from a blank page every time, characters, foreshadowing, and tone drift starting around episode 5. The ledger restores the state up to the previous episodeand prevents this drift.
- Planning is not something that ends once it is produced; rather, a living document updated with each episode다.
- This skill, separately from story creation (story-webtoon-planner·webnovel-writer), state managementhandles only that.
2. Two kinds of files
This skill creates two kinds of files. The filename convention is references/filename-convention.md.
| Deliverable | Nature | Filename | Creation timing |
|---|---|---|---|
| Full planning document | Series blueprint (worldview·characters·arc) | [작품제목]_기획서.md |
When planning a new series, created once, afterward only the status table is updated |
| Episode manuscript | The completed version of that episode (+visuals) | [작품제목]_EP##_[에피소드제목].md |
Each time each episode is written |
3. 2-mode entry (execute first)
The mode is determined by whether a planning document file exists.
Case A — Planning document exists (series re-invocation)
When the user presents an existing [작품제목]_기획서.mdor says "I have a planning document, make ep##":
- Read the entire planning document. Do not look only at the summary.
- Grasp the big picture:
- How many episodes have been released so far
- What emotional state the reader is likely in now (estimated from the flow of each episode)
- What role this episode should play in the overall arc
- What this episode must do for the series goal (a hit work)
- Based on that judgment, proceed directly to writing the episode.
⚠️ Do not just pull out and use each episode summary from the planning document. Design this episode by back-calculating from the overall flowis the reason this skill exists. The 5 principles of back-calculation are
references/recall-design.md.
Case B — No planning document (new planning)
Design a new master planning document. The skeleton is references/bible-template.md.
- Define the reader persona
- Worldbuilding design
- Character design (narrative info + visual sheet + consistency anchors)
- Series-wide arc + hook strategy
- Save the full planning document — Put the episode status table at the very bottom.
4. Invariant — episode generation = status table update
When you create an episode manuscript, you must update the episode status table in the planning document. They are always a set.
- If you do not update it, state restoration breaks on the next re-invocation.
- Status table schema: Episode / Status / Title / Core emotion / Hook point / File / Date. (
references/bible-template.md)
| ep## | ✅ 작성됨 | [에피소드제목] | [핵심 감정] | [훅 포인트 요약] | [파일명] | [날짜] |
5. Workflow summary
Step 0. 모드 확인 (기획서 유무)
Step 1. [신규] 마스터 기획서 설계 → 저장 + 현황표 삽입
[재호출] 기획서 전체 읽기 → 역산으로 이번 화 역할 판단
Step 2. 회차 원고 작성 (창작은 planner/webnovel-writer 체인에 위임 가능)
Step 3. 현황표 갱신 (불변식 — 반드시)
6. Worked example
Case A — "I have a planning document, make ep05"
우리집에는_철학자가_산다_기획서.mdRead the whole thing(not just the summary).- Confirm in the status table that ep01–04 are ✅, and use each episode's core emotion and hook to the reader's current emotion.
- If ep05 is at the beginning of the development section in the arc, judge that it is "when cracks begin to appear in the relationship."
- Following the 5 reverse-engineering principles (
references/recall-design.md) design this episode's events, emotions, and hooks, and write the manuscript. ..._EP05_...mdSave + update the ep05 row in the status table to ✅ (invariant).
Case B — "I want to start a webtoon series with this material"
- Since there is no planning document file, this is a new plan.
- Design reader persona → worldbuilding → characters (visual sheet · consistency anchors) → arc · hook strategy.
[작품제목]_기획서.mdSave, and insert an empty episode status table at the very bottom.- Subsequent episodes follow the Case A flow.
7. Consistency anchors (the core of preventing drift)
For each character, 1–2 things that must be fixed for each episodedecide and nail them down in the planning document (e.g., "silver hair + mole under the left eye," "cheese tabby + red bell collar"). If this wavers at the art stage, readers perceive them as a different character. Anchors go in the character section of the planning document along with the visual sheet (references/bible-template.md). In the episode manuscript, copy over only a summary of the anchors of characters appearing in that episode.
8. Notes
- Dedicated to state management. This skill does not do cut design or art. Cut scripts are
story-webtoon-episode, and art isstory-webtoon-art. - The visual sheet is separate from the main text. Character and space appearance details are gathered in the character section of the planning document and the visual items of the episode manuscript — do not list visual information in the story main text.
- Guests should be brief (but drawable). Since there is no consistency burden across multiple episodes, put only name and role in the full planning document, and the appearance details for that episode in the episode manuscript.
- Even an omnibus must have a throughline theme. A "mere collection of episodes" causes readers to drop off quickly.
- Follow the filename convention. Spaces→underscores, EP## two digits, remove forbidden characters (
references/filename-convention.md). - Do not copy summaries on re-invocation. Reverse-engineer from the overall flow (
references/recall-design.md) — The value of this skill is reading the overall flow.
9. Post-text-production review chain
Since episode manuscripts are text outputs, they go through the regular review chain after completion.
원고 초고 → moai-coworker:ai-slop-reviewer (1차 일반 후처리)
→ moai-writer:korean-humanize (2차 한국어 정밀 윤문)
Copyediting preserves meaning, proper nouns, figures, and quotationsand removes only the AI feel (not rewriting the content).
10. Related skills
| Relationship | Skill | Role |
|---|---|---|
| Before/After | story-webtoon-planner |
Webtoon story creation — this ledger supplies the state |
| Before/After | story-webnovel-writer |
Web novel creation — same ledger mechanism |
| Spec reference | story-webtoon-spec |
Check debut route, episode length, and monetization hooks |
| Lettering reference | story-webtoon-lettering |
Speech bubbles, typefaces, and SFX of the episode manuscript |
| Continuity audit | story-continuity-auditor (agent, Claude Cowork only) |
Verify multi-episode character, plot, and setting continuity (including Soul-ID) against the ledger. Since ChatGPT Work has no agent layer, split the request like "just review continuity against the ledger, don't fix anything, only point things out" to perform the same review |
| Post-review (text output) | moai-coworker:ai-slop-reviewer → moai-writer:korean-humanize |
First post-processing of manuscript text → second-pass precise Korean copyediting |
11. References
| File | Load condition |
|---|---|
references/bible-template.md |
When the master planning document skeleton and episode status table schema are needed |
references/filename-convention.md |
When deciding the output file name |
references/recall-design.md |
When reverse-engineering design and anti-pattern checks are needed on re-invocation |
Source
- Core asset: aitoon direction and planning system (internal asset port, adjusted to vertical scroll and Korean platform context).
- Original copywriter: Jo Nam-kyung (https://www.facebook.com/Bmisty)