chapter-production-flow

Orchestrates the end-to-end production lifecycle of BITM330 database-book chapters.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/nimdvir/dima-publishing --skill chapter-production-flow-nimdvir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chapter-production-flow
Source: https://github.com/nimdvir/dima-publishing/tree/main/.agents/skills/chapter-production-flow
Command: npx skills add https://github.com/nimdvir/dima-publishing --skill chapter-production-flow-nimdvir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Producing a textbook chapter involves many coordinated steps—editing prose, building companions like labs and RATs, managing media, tracking status, running final review, and exporting DOCX. This Skill orchestrates that entire multi-phase lifecycle so nothing is skipped and each task is delegated to the right specialized skill. ## Core Features & Use Cases - Lifecycle Orchestration: Runs phased production from preflight planning through editing, companions, media, terms, final review, and DOCX build. - Skill Delegation: Routes each domain task to specialized skills such as chapter-editor, lab-creation, term-creator, chapter-final-check, and chapter-docx-build. - Operational Records: Maintains progress logs, chapter-specific edit notes, and a cross-chapter tracker under the .edits directory. - Use Case: A course author asks to run the full production flow for Chapter 5; the Skill preflights the chapter folder, presents a plan for approval, delegates editing and companion work, runs the final readiness check, builds the DOCX, and produces a handoff summary. ## Quick Start Ask the assistant to run the full production flow for chapter 5 of the database book and approve the proposed plan.

Frequently Asked Questions about chapter-production-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage the full production workflow for a textbook chapter?▼

Provide a chapter number or folder path and optionally a mode such as full-flow, edit-main, or docx. The orchestrator runs a preflight check, presents a plan for approval, then delegates each phase to specialized skills and logs progress.

What production modes does the chapter workflow support?▼

Supported modes are plan-only, status, edit-main, companions, media, terms, final-review, docx, logs-only, full-flow, and handoff. If no mode is given, a numbered menu is presented before any files are written.

When should I use the orchestrator instead of a specialized chapter skill?▼

Use the orchestrator only when coordinating the full multi-step chapter lifecycle across several skills. For a single narrow task like editing prose, building a lab, or running the final readiness check, invoke that specialized skill directly.

Does the chapter production flow deploy or publish content?▼

No. The workflow explicitly prohibits deploying, publishing, committing, pushing, or merging. It stops after the DOCX build and handoff summary, leaving any deployment as a separate user-initiated action.

How does the workflow prevent answer files from leaking into source?▼

Preflight includes an answer-file exposure risk search across the source tree, and safety rules forbid leaving answer files under the canonical source directory. Final readiness verification is delegated to the chapter-final-check skill.