Book_Map Project Manager

VerifiedSafe

Scaffold, audit, and manage Book_Map writing projects. Creates missing files and directories according to a specification, checks compliance against a checklist, and adds new books with templates and handoffs. Helps writers and project managers maintain consistent structure across a book series.

Sby Skills Guide Bot
ContentIntermediate
6/2/2026
Claude Code
#book-map#book-series#project-scaffolding#manuscript-management

Recommended for

Automated summary

This skill scaffolds, audits, and manages a standardized Book_Map project structure for multi-book series, with subcommands to create, verify, and extend the project.

Strengths

  • Automates creation of a full directory and file structure for a book series.
  • Includes an audit command that checks compliance against a reference checklist and suggests remediation.
  • Provides a consistent workflow for adding new books with cross-referenced documentation and continuity updates.

Limitations

  • Requires the presence of reference documents (directory-spec.md, checklist.md, remediation.md) in the project.
  • Tied to the Book_Map framework; not adaptable to other organizational systems.
  • Does not overwrite existing files, which can lead to outdated templates if reference spec changes.
When to use it

When starting a multi-book series and you need a standardized, auditable project structure that enforces consistency across volumes.

When not to use it

For a single standalone book, projects with a different organizational scheme, or when you need real-time collaboration outside of Claude Code.

Security analysis

Safe
Quality score90/100

The skill instructs only file and directory creation within the project, reading reference specs, and reporting. No destructive commands, network calls, exfiltration, or obfuscated payloads are used. The absence of declared tools further limits execution risk.

No concerns found

How this analysis is made

Examples

Scaffold a new Book_Map project
Run /book-map scaffold to set up the complete Book_Map directory structure in the current project.
Audit an existing Book_Map project
Run /book-map audit to check if the current project conforms to the Book_Map standard and report any issues.
Add a new book to the series
Run /book-map add-book to create the next book directory and all required files, updating indexes and handoff documents.

/book-map

Scaffold, audit, and manage Book_Map projects.

Subcommands

/book-map scaffold

Scaffold the Book_Map structure in the current project directory.

Instructions for Claude:

  1. Read references/directory-spec.md for the complete file/directory specification.
  2. Create all required directories that do not exist.
  3. Create all required files that do not exist, using appropriate templates.
  4. For each file created, add the <!-- reviewed: YYYY-MM-DD --> freshness tag with today's date.
  5. Do NOT overwrite existing files — only create missing ones.
  6. After scaffolding, run the audit subcommand to verify completeness.

Output format:

Created: [list of files/dirs created]
Skipped: [list of files/dirs that already existed]
Run `/book-map audit` to verify completeness.

/book-map audit

Audit the current project against the Book_Map standard.

Instructions for Claude:

  1. Read references/checklist.md for the audit criteria.
  2. Check each criterion and report pass/fail.
  3. For each failure, reference references/remediation.md for the fix.
  4. Report an overall score (pass count / total count).

Output format:

Book_Map Audit Results
======================
[Category]: [pass/fail count]
  ✓ criterion description
  ✗ criterion description → fix: [remediation step]

Overall: [total pass] / [total checks] passed

/book-map add-book

Add a new book to the series.

Instructions for Claude:

  1. Determine the next book number by checking existing books/book-NN/ directories.
  2. Create the book directory structure:
    books/book-NN/
      manuscript/
        _INDEX.md
        front_matter/.gitkeep
        chapters/
        back_matter/.gitkeep
      docs/
        _INDEX.md
        book/
          OVERVIEW.md
          OUTLINE.md
          CONTINUITY_BIBLE.md
    
  3. Populate each file with appropriate templates:
    • manuscript/_INDEX.md — empty chapter status table
    • docs/_INDEX.md — per-book doc index linking to book-specific and shared docs
    • docs/book/OVERVIEW.md — minimal book premise referencing series arc
    • docs/book/OUTLINE.md — empty outline with contract format
    • docs/book/CONTINUITY_BIBLE.md — initialized from previous book's final state
  4. Add the new book to books/_INDEX.md.
  5. Create a handoff template at series/handoffs/BOOK-NN-TO-MM.md (from previous book to this one).
  6. Update docs/_INDEX.md to include the new per-book documents.

Output format:

Created book-NN:
  books/book-NN/manuscript/_INDEX.md
  books/book-NN/manuscript/front_matter/.gitkeep
  books/book-NN/manuscript/chapters/
  books/book-NN/manuscript/back_matter/.gitkeep
  books/book-NN/docs/_INDEX.md
  books/book-NN/docs/book/OVERVIEW.md
  books/book-NN/docs/book/OUTLINE.md
  books/book-NN/docs/book/CONTINUITY_BIBLE.md

Updated:
  books/_INDEX.md
  series/handoffs/BOOK-[prev]-TO-NN.md
  docs/_INDEX.md

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/book-map-project-manager-mma3jr2i/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/book-map-project-manager-mma3jr2i' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/book-map-project-manager-mma3jr2i/download' --output '.skill-downloads/book-map-project-manager-mma3jr2i/SKILL.md.part' && mv '.skill-downloads/book-map-project-manager-mma3jr2i/SKILL.md.part' '.skill-downloads/book-map-project-manager-mma3jr2i/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/book-map-project-manager-mma3jr2i/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills