chapter-command-center

Routes BITM330 chapter production requests to the appropriate specialized skill.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on BITM330 database-book chapters, it is often unclear which production skill should handle a given request, leading to misrouted tasks or overly broad workflows. This Skill interprets the user's goal, identifies the chapter state, and recommends the smallest appropriate skill with an exact suggested invocation. ## Core Features & Use Cases - Request Routing: Maps user goals like editing, media cleanup, companion creation, final review, or DOCX builds to the correct specialized skill. - Decision Support: Answers "what should I do next?" by interpreting chapter status and recommending a next action with reasoning. - Ambiguity Handling: Asks at most one clarifying question when the chapter or task is unclear, defaulting to a plan-only route when uncertain. - Use Case: A user asks "What should I do next for Chapter 9?" and receives a recommendation to run chapter-production-flow in plan-only mode, with an explanation of what it will and will not do. ## Quick Start Ask what to do next for a specific chapter, such as requesting a recommended next step for ch09, and receive a routing recommendation with a suggested skill invocation.

Frequently Asked Questions about chapter-command-center

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

FAQPage Schema
How do I decide which skill to use for a book chapter task?▼

Describe your goal in plain language, such as editing prose, fixing images, or checking readiness. The command center maps your request through its routing table and returns the recommended skill with a suggested invocation and reasoning.

How do I find out what to do next for a chapter?▼

Ask for the next step with a chapter number, for example ch09. The command center typically routes status and planning questions to chapter-production-flow in plan-only mode rather than launching a full workflow.

Does the command center edit chapter content or media itself?▼

No, it is a router only. It never edits prose, rewrites companions, optimizes media, builds DOCX, or updates trackers; it delegates those tasks to specialized skills like chapter-editor or chapter-media.

What happens when my request is ambiguous or missing a chapter?▼

The command center asks at most one clarifying question, such as which chapter to use. If both the chapter and task are unclear, it asks a combined question, and when uncertain it recommends chapter-production-flow plan-only.

Can the command center run sync, deploy, or commit actions?▼

No. It never suggests or runs sync, deploy, publish, commit, push, or merge unless explicitly requested, and it requires user approval before any write-producing skill is launched.