Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From velith
Multi-phase book publishing pipeline with genre-specific workflows for fiction, non-fiction, technical, and other formats. Handles ideation through export with quality gates at each stage.
npx claudepluginhub epicsagas/plugins --plugin velithHow this skill is triggered — by the user, by Claude, or both
Slash command
/velith:loomThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build books like software. 6-phase pipeline from blank page to published book, with dedicated skills, agents, and quality gates at every stage.
Manages multi-book content, voice, and production workflows for nonfiction authoring. Plan books, maintain consistent voice, structure manuscripts, and run end-to-end publishing pipelines.
Provides structured guidance for writing blogs, research articles, fiction, essays, and marketing copy, including audience analysis, outlining, drafting, revising, and polishing.
Routes users to the correct book genre (fiction, non-fiction, technical, screenplay, poetry, game, academic) or helps compose a custom genre from existing patterns.
Share bugs, ideas, or general feedback.
Build books like software. 6-phase pipeline from blank page to published book, with dedicated skills, agents, and quality gates at every stage.
Phase 0: Onboarding → Phase 1: Ideation → Phase 2: Outlining → Phase 3: Drafting → Phase 4: Editing → Phase 5: Publishing
| Genre | Key Differences | Reference File |
|---|---|---|
| Fiction | Plot structure (Save the Cat!/Snowflake), character bible, scene beats | book-fiction |
| Non-Fiction | Problem-solution structure, persona-driven, evidence hierarchy | book-nonfiction |
| Technical | Concept progression (novice→expert), code examples, diagrams, API docs | book-technical |
| Screenplay | 3-act + sequence method, dialogue/action, A/B story | book-screenplay |
| Poetry | Form-driven (sonnet/haiku/free verse), imagery systems, collection arc | book-poetry |
| Game | Quest trees, branching dialogue, lore bible, flag system | book-game |
| Academic | IMRAD, literature review, argument chains, citation practices | book-academic |
| Custom | Compose patterns from any genre via book-genre-creator | book-genre-creator |
When /velith is invoked without arguments, detect current project state and route:
Detection: check for drafts/ directory, outline.md, STYLE.md, PRD.md in current project.
/velith onboard)STYLE.md (voice, tone, conventions)PRD.md (book requirements)/velith ideate)ideation.md/velith outline)outline.mdbook-architect validates structure/velith draft)scene-generator decomposes chapters into scenes first (fiction only)chapter-writer generates each chapter (from scenes if available)continuity-editor checks cross-chapter consistency/velith edit)style-doctor enforces voice consistency/book-publish)cover-designer → concepts + image promptsmarketing-expert → launch strategy{project-dir}/
├── PRD.md # Book requirements (Phase 0)
├── STYLE.md # Voice, tone, conventions (Phase 0)
├── ideation.md # Ideas, market research (Phase 1)
├── outline.md # Full chapter outline (Phase 2)
├── drafts/ # Chapter drafts (Phase 3)
│ ├── ch00-foreword.md
│ ├── ch01-xxx.md
│ └── ...
├── edits/ # Editing reports (Phase 4)
│ └── editorial-report.md
├── publish/ # Final outputs (Phase 5)
│ ├── book.epub
│ ├── book.pdf
│ └── metadata.yaml
└── sources/ # Source material references
Each phase has a dedicated skill in skills/book-{name}/SKILL.md:
| Skill | Phase | Description |
|---|---|---|
book-init | 0 | Project setup, genre selection, STYLE.md + PRD.md |
book-ideation | 1 | Market research, concept distillation, scope |
book-outline | 2 | Chapter outline with dependencies and cross-references |
book-draft | 3 | Plan-Then-Execute chapter generation |
book-edit | 4 | 5-stage editing pipeline |
book-publish | 5 | EPUB/PDF/MOBI packaging, cover, marketing |
book-status | — | Project status dashboard and web UI |
book-fiction | — | Fiction patterns (Save the Cat!, character bible) |
book-nonfiction | — | Non-fiction patterns (problem-solution, persona) |
book-technical | — | Technical book patterns (concept progression, code) |
book-screenplay | — | Screenplay patterns (3-act + sequence method, dialogue) |
book-poetry | — | Poetry patterns (form types, imagery systems, collection) |
book-game | — | Game scenario patterns (quest trees, branching, lore) |
book-academic | — | Academic patterns (IMRAD, lit review, argument chains) |
book-genre-creator | — | Meta-skill for genre selection and custom genre creation |
| Agent | Role | When |
|---|---|---|
book-architect | Structure validation, outline generation | Phase 2 |
chapter-writer | Chapter draft generation | Phase 3 |
continuity-editor | Cross-chapter consistency check | Phase 3-4 |
style-doctor | Voice and tone consistency | Phase 4 |
scene-generator | Scene-level breakdown with GMC+RDD (fiction only) | Phase 3, fiction |
cover-designer | Cover concepts + image generation prompts | Phase 5 |
marketing-expert | Reader personas, channel strategy, launch calendar | Phase 5 |
Each phase has mandatory completion criteria before proceeding:
| Phase | Gate | Evidence |
|---|---|---|
| 0 | Project initialized | PRD.md + STYLE.md exist |
| 1 | Concept validated | Elevator pitch + 3 competing titles analyzed |
| 2 | Outline complete | All chapters specified + cross-reference map |
| 3 | Drafts complete | All chapters meet word target + frontmatter |
| 4 | Editing complete | 5-stage pipeline passed + <5 issues remaining |
| 5 | Publish ready | EPUB/PDF generated + metadata complete |