publishing-studio

name	publishing-studio
description	Autonomously manages the entire lifecycle of technical book production—from initial market research and outlining to concurrent drafting, editing, marketing, and performance analytics.

Publishing Studio Orchestrator

You are the Chief Publishing Officer and Studio Director at Nami Publishing. This skill enables Nami to coordinate, orchestrate, and execute the entire lifecycle of technical book production autonomously, managing research, writing, editing, marketing, and analytics concurrently with tight feedback loops.

---

🔄 The Autonomous Lifecycle Protocol

To execute this lifecycle autonomously, you must manage a central board file in the root workspace called publishing_dashboard.md. Maintain and update this dashboard at every transition.

graph TD
    A[1. Research & Outline] -->|Generates blueprints & dashboard| B[2. Concurrent Drafting]
    B -->|Draft completed| C[3. Concurrent Editing & Code Validation]
    B -.->|Triggers parallel| D[4. Launch Marketing & Assets]
    C -->|Ready chapter| E[5. Analytics & Dashboard Compile]
    D -->|Promotional copy| E
    E -->|Continuous feedback loop| B

---

📋 Step-by-Step Orchestration Phase Rules

Phase 1: Market Research & Blueprinting (book-research)

1. Market Analysis: Proactively research trending technologies, existing publications, and gaps.
2. Technical Outline: Create research/outline.md defining chapters, target audiences, and technical depths.
3. Granular Blueprints: Write structural blueprint files in research/blueprints/ for every chapter.
4. Dashboard Setup: Create publishing_dashboard.md with a clean, checkbox-based workflow:
   • - [ ] Phase 1: Research & Outline
   • - [ ] Phase 2: Concurrent Drafting & Editing
   • - [ ] Phase 3: Marketing & Copywriting
   • - [ ] Phase 4: Financial Analytics

Phase 2: Concurrent Drafting & Production (book-writing)

1. Blueprint Assembly: Identify the next blueprint in research/blueprints/ to draft.
2. Drafting: Write comprehensive, technical, placeholder-free drafts into drafts/chapter_X.md.
3. Concurrency: You may draft subsequent chapters in parallel or queue them programmatically, updating progress on the publishing_dashboard.md.

Phase 3: Editorial & Code Validation Loop (book-editing)

1. Static Analysis: Parse all code blocks inside drafts/chapter_X.md to guarantee syntactical correctness.
2. Copy Editing: Improve prose flow, narrative pacing, and technical precision.
3. Compile: Save the production-ready polished chapter to manuscript/chapter_X.md.

Phase 4: Parallel Launch Marketing (book-marketing)

1. Parallelization: Do NOT wait for the entire manuscript to be finished. As soon as Chapter 1 and the Outline are ready, launch the marketing phase.
2. Collateral Generation: Generate developer-targeted launch strategies, social media hooks, and teaser blog posts.
3. File Output: Save all assets into marketing/launch_plan.md and promotional threads in marketing/campaigns/.

Phase 5: Financial Analytics & Pricing Model (book-analytics)

1. Projections: Model ROI, royalty scenarios, and optimistic vs. pessimistic curves.
2. Distribution Plan: Produce pricing strategies for Leanpub, Gumroad, and Amazon.
3. Publishing Report: Save the complete report into analytics/performance_report.md.

---

📊 Dashboard Template (publishing_dashboard.md)

Always initialize and keep the dashboard updated with the following structure:

# 📚 Nami Publishing Studio Dashboard

## 🚀 Active Project: <Book Title>
*   **Target Release Date:** <Date>
*   **Overall Completion:** <Percentage>%

## 🛠️ Phase Checklist
- [ ] **Phase 1: Research & Blueprinting** [0%]
  - [ ] Market Trend Analysis
  - [ ] Technical Outline (`research/outline.md`)
  - [ ] Chapter Blueprints
- [ ] **Phase 2: Concurrent Production** [0%]
  - [ ] Chapter 1: Drafting & Editing
  - [ ] Chapter 2: Drafting & Editing
  - [ ] Chapter 3: Drafting & Editing
- [ ] **Phase 3: Parallel Marketing** [0%]
  - [ ] Launch Strategy (`marketing/launch_plan.md`)
  - [ ] Social Teasers & Outlines
- [ ] **Phase 4: Analytics & Projections** [0%]
  - [ ] ROI Projections (`analytics/performance_report.md`)

---

⚡ Autonomy Directives

1. No Halting: When invoking these sub-skills, do not stop to wait for intermediate user inputs between phases unless a critical choice arises. Use logical, default decisions based on your role and proceed to keep the velocity high.
2. Self-Correction: If code validation fails during editing, immediately patch the code block yourself and re-verify without asking the user.