the framework of the webtoon frameworkThis is the skill that builds [it]. By deciding the worldbuilding, serialization structure, series arc, and hook strategy, it creates a planning document that keeps the state ledger (story-series-bible), characters (story-character-sheet), and episodes (story-webtoon-episode) that follow from wavering. If the planning leaks, the episodes drift more and more as they go on.
1. Overview
This skill focuses on the planning judgment of **"what to serialize, and in what structure."** Specs such as canvas width, number of panels per episode, and debut path are not decided here story-webtoon-spec and are referenced from the hub. Specs change with time and policy, so they are managed in only one place (the hub).
2. What this skill does not do
- Does not assert spec numbers — canvas width, episode vertical length, panel count, and debut path promotion criteria are owned by
story-webtoon-specThis skill only references those values. - Does not create character visual sheets — the 8-item appearance table, consistency anchors, and neutral default form are
story-character-sheetunder story-character-sheet's purview. - Does not do episode panel breakdown or staging — the panel script is
story-webtoon-episode, and lettering isstory-webtoon-lettering. - Does not save files or update state — saving the planning document and the episode status table are owned by
story-series-bibleThis skill designs the planning content and hands it over.
3. Preliminary check — fix the specs first
Before starting planning, check the specs first. Reference the following two files from the story-webtoon-spec hub.
${CLAUDE_PLUGIN_ROOT}/skills/story-webtoon-spec/references/platform-debut-paths.md— target platform and debut path (Naver Webtoon Challenge Comics → Best Challenge → official serialization, 3 stages 등).${CLAUDE_PLUGIN_ROOT}/skills/story-webtoon-spec/references/episode-volume.md— Season 1 episode scale and serialization cycle (fill the episode-count column in the series arc table below with these values).
⚠️ Do not arbitrarily assert the episode count of a series arc as "20 episodes, complete." Since the Season 1 specs for official Korean serialization may differ from this,
episode-volume.mdreflect the value (or the[미확인]flag) as is.
4. Workflow
Step 1 — Worldbuilding design
Organize the setting, era, core rules, and taboos. Summarize in one sentence so that "what is especially different in this world" becomes a hook rather than an entry barrier for readers.
Step 2 — Webtoon-native reader assessment (2 questions)
Verify with two questions whether the plan suits a vertical-scroll webtoon. If even one is "no," revisit the structure.
- Is the reason for pressing the next-episode button clear in every episode? — What are they curious about that makes them turn the page?
- When you have 5 minutes left on the subway, do you click this webtoon? — Is it a rhythm consumed in brief gaps?
Step 3 — 3-way classification of serialization structure + genre mapping
First choose which structure to serialize with. The structure governs everything about episode design and hook placement.
| Structure | Characteristics | Suitable genres |
|---|---|---|
| Episodic standalone type | Each episode is self-contained. OK to read anytime | Slice of life · Healing |
| Continuous narrative type | The entire story continues | Drama · Fantasy |
| Hybrid type | Episode-level completion + an overarching larger flow | Most popular works |
Genre-specific character trees, conflict structures, and hook tendency presets are references/genre-presets.md.
⚠️ Even an omnibus (episodic standalone type) loses readers quickly without a throughline theme. A "mere collection of episodes" has weak holding power — you must decide the throughline theme from Step 5.
Step 4 — Series arc design
Divide the entire serialization into segments and place each segment's role, key events, and emotional tone. The episode count column is filled with the episode-volume.md value(The numbers below are only an example skeleton, not a definitive claim).
| Segment | Episode count | Role | Key events | Emotional tone |
|---|---|---|---|---|
| Introduction | [episode-volume.md 참조] |
Worldview · character introduction | ||
| Development | [참조] |
Relationship formation, conflict begins | ||
| Climax | [참조] |
Core conflict explodes | ||
| Resolution | [참조] |
Resolution, growth |
Step 5 — Throughline theme in one sentence
Nail down in one sentence the core theme that will not waver across multiple segments.
"What this webtoon ultimately wants to say is ___."
Step 6 — Hook strategy + regular cast cap
- Hook type placement: Episodes 1–3 grab readers with character hooks + emotional hooks, and from the midpoint onward, curiosity hooks are gradually planted. Aligning the paid conversion point with hooks is done at the
story-webtoon-episode의monetization-hooks.mdreference stage. - Regular cast cap: Declare the regulars appearing in every episode as no more than 5. As the number of people increases, the burden of maintaining consistency per episode and (when adapted to webtoon) generation credits both increase — the cast cap is directly tied to cost control. Move the excess to guests.
5. Output format
Organize the planning content in master planning document format and hand it over to story-series-bibleto save (this skill does not save).
# [작품제목] 기획서 (초안)
## 세계관
- 배경·시대·핵심 룰·금기
## 연재구조
- 분류: [에피소드 독립형 / 연속 서사형 / 혼합형]
- 장르: [ ] → genre-presets 적용
## 관통 주제
> 이 웹툰이 결국 하고 싶은 말은 ___이다.
## 시리즈 아크
| 구간 | 화수(spec 참조) | 역할 | 핵심 사건 | 감정 톤 |
| ... |
## 훅 전략
- 구간별 훅 유형·강도
## 레귤러 상한
- 레귤러 N명(≤5) / 나머지는 게스트
→ Saving and episode status table generation are handed over to story-series-bible.
6. Precautions
- Do not duplicate specifications. Do not hardcode canvas, debut, or episode count figures into this skill's body — refer to the hub.
- Do not hallucinate episode counts. Do not write arbitrary numbers like "20-episode completion" as if they were facts.
- When the regular-member cap of 5 is exceeded, consistency and cost both collapse. Separate them into a guest tier.
- If it fails the two reader-judgment questions, even if the subject matter is good, it doesn't fit the vertical-scroll rhythm — re-examine the structure from the start.
7. Related Skills
Before
story-project— Entry router (webtoon line judgment)story-webtoon-spec— Spec SSOT (debut route and episode length verification)
After
story-series-bible— Save planning document + generate episode status table (state establishment)story-character-sheet— Character visual sheet and consistency anchorsstory-webtoon-episode— Episode plot and cut breakdown
Post (review — standard text-output chain)
moai-coworker:ai-slop-reviewer— AI slop review (required)moai-writer:korean-humanize— Precise AI-ness polishing (required)
⚠️ The planning document's prose (worldbuilding, theme, arc description) is read not by readers but by collaborators, yet since it leads into later episode dialogue and narration, it goes through the standard text chain.
8. References
| File | Load Condition |
|---|---|
references/genre-presets.md |
When you need a genre-specific character tree, conflict structure, and hook tendencies |
../story-webtoon-spec/references/platform-debut-paths.md |
Target platform and debut route verification |
../story-webtoon-spec/references/episode-volume.md |
Series arc episode count and serialization cycle verification |
9. Sources
- Serialization structure 3-way classification, series arc table, overarching theme, two reader-judgment questions, regular-member cap: aitoon-plot planning system (internal asset port).
- Platform spec facts:
story-webtoon-spechub (official guide URLs for each reference). - Original copywriter: Cho Nam-kyung (https://www.facebook.com/Bmisty)