book-writer

Orchestrate a full book-writing workflow from topic to finished EPUB with cover image. Use when the user asks to "write a book", "draft a book", "author a book", "책 쓰기", "책 저술해줘", "책 만들어줘", "전자책 만들어줘", "EPUB 생성", provides a topic/audience/outline and asks to turn it into a book, or says "~에 대한 책을 써줘". Also triggers on follow-ups like "다시 저술", "계획 수정", "챕터 다시 써줘", "표지 바꿔", "책 업데이트", "특정 챕터 보완", "이전 책 개선", "리서치만 다시". Coordinates research, planning, review, chapter writing in the active genre voice (auto-detected; defaults to tech-book = Toby's style), style enforcement, editing, cover design, and EPUB assembly. Author defaults to Toby-AI (overridable via user prompt — include "저자: {이름}").

Integrate all finished chapters into a single book-ready manuscript — polish chapter transitions, unify terminology, insert cross-chapter callbacks, and write front/back matter (preface, epilogue, references). Produce a manuscript + book_manifest.json for EPUB build. Use when chapters are individually complete and need to become a coherent book.

Design the overall book structure — title candidates, characteristics, chapter list with main content per chapter, and narrative arc. Use when turning research into a writing plan, drafting a book outline, planning chapter sequence, or revising a book plan based on review feedback. Triggers on "저술 계획", "책 아웃라인", "챕터 구성", "book outline".

Write a single book chapter in Toby's distinctive Korean writing style (평어체 기반, 청유형 적극 활용, 수사적 질문, 상황 가정, 감정적 공감 표현). Use when drafting or revising a book chapter, rewriting prose in Toby's voice, translating an outline into full chapter text, or polishing chapter drafts to match 토비 문체. Triggers on "챕터 써줘", "이 섹션 저술", "토비 스타일로 써줘", "write a chapter in Toby's voice", "rewrite in 평어체", or when a chapter outline needs to become full prose.

Build a standards-compliant EPUB 3 file from a manuscript markdown, cover image, and book_manifest.json using the bundled pandoc-based script. Output is 책-제목-v{version}.epub with the manifest's author (defaults to Toby-AI), accompanied by a paired 책 소개 markdown ({책-제목}-v{version}.md) in the same folder. Use when converting the final book manuscript to EPUB, rebuilding after edits, or testing EPUB output.

Verify concrete factual claims in a tech-book chapter draft — numbers, statistics, benchmarks, quotes, version numbers, release years, API signatures, superlatives — against the reference document, and resolve "(사실 확인 필요)" markers. Use when checking a chapter for factual accuracy, validating version/API claims in fast-moving tech content, or resolving fact-check annotations. Triggers on "팩트체크", "사실 확인", "fact check", "출처 검증", "버전 맞는지 확인".

Whole-book acceptance gate run by a fresh-context reviewer before EPUB build (Phase 4.5). Cross-reads the integrated manuscript against the plan and escalation logs, scans for forbidden leftover markers, checks terminology/cross-reference/promise integrity, and emits {slug}/05_acceptance.md with per-criterion PASS/BLOCK + routing. Genre-agnostic; complements (does not replace) per-chapter fact/continuity loops. Triggers on "수락 검수", "통권 검수", "manuscript acceptance", "최종 통과 게이트".

Coordinate parallel research agents (web, paper, community) and synthesize findings into a unified reference document. Use when collecting background material for a book, whitepaper, or deep-dive article — triggers on "리서치 조율", "여러 소스에서 자료 모아줘", "reference 문서 만들어줘" style requests. De-duplicates, groups by theme, flags conflicts, preserves citations.

Review chapter drafts against the active genre profile's style checklist (defaults to tech-book = Toby's voice) — detects voice deviations and provides concrete before/after rewrite suggestions. Use when reviewing a chapter draft for style consistency, enforcing the genre voice, or polishing prose.

Maintain a story bible and check narrative chapter drafts for continuity — character facts (appearance, voice, motive), relationships, world rules, timeline, and planted setups (복선). Seeds {slug}/story_bible.md from the plan, flags contradictions, and tracks setup→payoff. Use when keeping a novel consistent across chapters, building a story bible, validating character voice, or tracking 복선. Triggers on "연속성 확인", "스토리 바이블", "복선 추적", "캐릭터 일관성", "continuity check", "story bible".

Mine developer/practitioner communities (Reddit, Hacker News, StackOverflow, GitHub Discussions, OKKY, velog, 네이버 카페) for real-world pain points, debates, and field-tested heuristics. Use when the user asks for "커뮤니티 의견", "실무자 목소리", "Reddit·HN 뒤져줘", "현장 경험담 모아줘", or when a book needs authentic pain-point material for chapter openings.

Search the general web (blogs, articles, official docs, tutorials) for topic-relevant content and compile findings with full citations. Use when the user asks to "웹 리서치", "블로그 자료 모아줘", "공식 문서 뒤져줘", "search the web for", "find articles on", or when gathering secondary material outside academic/community sources.

Generate a book cover image (1600x2560 PNG) based on title, topic mood, and target audience. Craft image generation prompts in English, use available image-gen MCPs or APIs, fallback to ImageMagick typography. Use when creating, revising, or A/B testing book covers. Author attribution defaults to Toby-AI (override via orchestrator input).

Search academic sources (arXiv, Google Scholar, Semantic Scholar, ACM, IEEE) for research papers and extract theoretical foundations, methods, empirical findings, and citation-worthy claims. Use when the user asks for "논문 리서치", "학술 자료", "arXiv에서 찾아줘", "papers on", or when a book/article needs rigorous academic backing.

Critically review a book plan against the reference document and audience fit. Check coverage, narrative flow, audience alignment, chapter balance, and redundancy. Use when reviewing a book outline, auditing a chapter structure, or giving structured feedback on a writing plan. Triggers on "계획 리뷰", "아웃라인 평가", "review the plan", "critique the outline".