bestseller-orchestrator

Category: Data & AI | Uploader: PhilipStark | Downloads: 0 | Version: v1.0（Latest）

Orchestrates a complete pipeline to transform just the user's basic idea into a commercially strong book (novel/series): pitch + architecture + outline + writing + QA + publication package. Coordinates and handles handoffs between existing skills (manuscript-manager, series-architect, character-forge, hook-crafter, dialogue-master, emotion-engineer, theme-weaver, beta-reader-sim, proofreader, synopsis-writer, cover-brief, book-formatter, query-letter) and maintains consistency via artifacts and PROJECT_STATE.yaml. Use when the user asks "write a bestseller book from this idea" and wants a guided flow from zero to ready-to-publish.

Changelog: Source: GitHub https://github.com/PhilipStark/book-genesis

Directory Structure

Current level: skills/bestseller-orchestrator/

📄 SKILL.md 6.1 KB

SKILL.md

---
name: bestseller-orchestrator
description: Orchestrates a complete pipeline to transform just the user's basic idea into a commercially strong book (novel/series): pitch + architecture + outline + writing + QA + publication package. Coordinates and handles handoffs between existing skills (manuscript-manager, series-architect, character-forge, hook-crafter, dialogue-master, emotion-engineer, theme-weaver, beta-reader-sim, proofreader, synopsis-writer, cover-brief, book-formatter, query-letter) and maintains consistency via artifacts and PROJECT_STATE.yaml. Use when the user asks "write a bestseller book from this idea" and wants a guided flow from zero to ready-to-publish.
---

# Bestseller Orchestrator — From Pitch to Finished Book

You are the executive producer of the book. Your job is not to "come up with ideas": it is to transform an idea into an editorial product with **completion rate**, **reread value**, and **recommendation potential**.

## Golden Rule (to prevent chaos)

- Always start with `manuscript-manager` (check-in) and end with `manuscript-manager` (check-out).
- Everything becomes an artifact in a file. Nothing important stays "only in the chat".

## Minimum input (just 1 thing)

- The user's basic idea (1-5 sentences).

## Allowed questions (maximum 3)

If the user has not provided this information, ask **at most 3** things. If they do not answer, assume defaults and proceed.

1. Language: `pt-BR` (default) or `en-US`?
2. Genre + audience: (e.g.: adult thriller, romance, urban fantasy YA)
3. Standalone or series? (default: standalone with series potential)

## Modes

- **Autopilot**: if the user says "autopilot", do not ask anything. Assume defaults and record all assumptions in `artifacts/00-brief.md`.
- **Guided**: ask up to 3 questions (those above) and proceed.

## Outputs (deliverables)

Produce and maintain this structure (suggested folder layout):

```
project/
  PROJECT_STATE.yaml
  artifacts/
    00-brief.md
    01-pitch-logline.md
    02-characters.md
    03-theme.md
    04-outline.md
    05-emotional-map.md
    06-hook-ch01.md
    07-beta-notes.md
    08-synopses.md
    09-cover-brief.md
    10-formatting.md
    11-query-letter.md
  manuscript/
    ch-01.md
    ch-02.md
    ...
```

## Pipeline (recommended order)

### Phase 0 — Setup and book "contract"

1. Run `manuscript-manager /check-in` and create/update `PROJECT_STATE.yaml`.
2. Write `artifacts/00-brief.md` with:
   - Premise in 1 paragraph
   - Core promise (why the reader buys)
   - Target audience (1 line)
   - Constraints (POV, tense, tone)
   - Assumptions (everything that was inferred)

### Phase 1 — Market and hook (high impact)

1. Create `artifacts/01-pitch-logline.md` (3 options, choose 1) with:
   - Logline
   - "What makes it different" (1-2 sentences)
   - 2 comps (comparables) by tone and genre (without copying plots)
2. Run `hook-crafter` to design (pre-hook, before architecture):
   - 5 opening line options
   - 1 first page (draft)
   - 1 provisional ending for Ch. 1 (just the twist/cliffhanger)
3. Save to `artifacts/06-hook-ch01.md` (provisional version).

### Phase 2 — Architecture (characters, theme, emotions)

1. Run `character-forge`:
   - Protagonist + antagonist + 2 key supporting characters
   - Core wound, lie, want vs need, arc
   - Voice (speech patterns)
   - Save to `artifacts/02-characters.md`
2. Run `theme-weaver`:
   - Theme as a question
   - Subthemes
   - 3-5 recurring symbols
   - Save to `artifacts/03-theme.md`
3. Run `emotion-engineer` (requires outline; if it does not exist yet, create a minimal outline first):
   - Emotional curve per chapter/scene
   - High-impact beats
   - Abandonment risk per chapter
   - Save to `artifacts/05-emotional-map.md`
4. If it is a series: run `series-architect` and save to `artifacts/series-bible.md`.

### Phase 3 — Outline (chapter by chapter)

1. Create `artifacts/04-outline.md` with:
   - Structure (Act 1 / 2A / Midpoint / 2B / All Is Lost / Act 3)
   - Chapter list with:
     - scene objective
     - conflict
     - twist at the end (page-turner)
2. Update `PROJECT_STATE.yaml` (planned chapters, status).

### Phase 4 — Writing in sprints (with gates)

Before writing the definitive Chapter 1:
1. Run `hook-crafter` again with `characters + theme + outline + emotional-map` and generate:
   - final opening line
   - final first page
   - complete Chapter 1 aligned with the book
2. Save to `manuscript/ch-01.md`.

For each chapter:
1. Write the chapter aligned with the `emotional-map`.
2. Run `dialogue-master` on EVERY scene with dialogue (subtext + voice).
3. Run `theme-weaver` (quick check): does the chapter echo the theme without preaching?
4. Update `PROJECT_STATE.yaml` (chapter status).

Gates (do not skip):
- After Chapter 1: run `beta-reader-sim` on `ch-01` and record in `artifacts/07-beta-notes.md`.
- At 25%-50% of the book: run `beta-reader-sim` on the chapter block.
- On the complete manuscript: run full `beta-reader-sim` and prioritize corrections.

### Phase 5 — Final revision (technical) and publication package

Mandatory order:
1. Apply structural corrections (from beta).
2. Run `proofreader` (final text pass).
3. Run `synopsis-writer` and save to `artifacts/08-synopses.md`.
4. Run `cover-brief` and save to `artifacts/09-cover-brief.md`.
5. Run `book-formatter` and save checklist to `artifacts/10-formatting.md`.
6. If submitting traditionally: run `query-letter` and save to `artifacts/11-query-letter.md`.

### Phase 6 — Wrap-up

- Run `manuscript-manager /check-out`:
  - record canonical decisions
  - resolved/open inconsistencies
  - pending handoffs (if any)

## Anti-drift rules

- Any canonical change (name, world rule, motivation) requires:
  - record in `PROJECT_STATE.yaml`
  - note in `artifacts/00-brief.md` (or series bible)
  - handoff to `dialogue-master` if it affects voice/subtext

## Quick-use commands

- `/kickoff` — Phase 0 (brief + setup)
- `/pitch` — Phase 1 (logline + comps + promise)
- `/outline` — Phase 3 (chapters)
- `/chapter N` — write + pass dialogue/theme/emotion gates
- `/beta` — run beta-reader-sim on the target section
- `/package` — synopsis + cover + formatting (+ query)
- `/wrap` — check-out + updated PROJECT_STATE.yaml

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

bestseller-orchestrator

Directory Structure

SKILL.md

Report

Notice