project-book

Assemble multi-thread chapter projects into a compiled LaTeX book.

1|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/rjwalters/bucket-brigade --skill project-book
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-book
Source: https://github.com/rjwalters/bucket-brigade/tree/main/.anvil/skills/project-book
Command: npx skills add https://github.com/rjwalters/bucket-brigade --skill project-book

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple independent chapter threads—each with its own version history, review state, and convergence progress—into a single cohesive compiled book is a manual, error-prone process that breaks down as projects scale.

Core Features & Use Cases

  • Automated Chapter Staging: Resolves the latest version of every chapter thread and stages it into a consumer-owned master LaTeX document.
  • Two-Pass PDF Compilation: Compiles the assembled book with XeLaTeX (two-pass) to produce a final book.pdf deliverable.
  • Convergence Reporting: Generates a BOOK_REPORT.md detailing each thread's resolved version, lifecycle state, review score, and audit status.
  • Graceful Degradation: Empty threads or threads below readiness thresholds generate placeholder chapters and warnings rather than blocking the build.

Quick Start

Use the project-book skill to assemble the chapters of your multi-thread project into a compiled book PDF.

Frequently Asked Questions about project-book

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

FAQPage Schema
How do I compile multiple independent chapter threads into a single LaTeX book?

To compile multiple chapter threads into a LaTeX book, you need a project root with a BRIEF.md listing documents and a master LaTeX document. The skill stages the latest version of each thread and compiles them into a book.pdf.

What is needed to automate XeLaTeX document assembly for a multi-thread writing project?

XeLaTeX document assembly requires a consumer-owned master LaTeX document, a XeLaTeX toolchain, and a project root containing a BRIEF.md with a documents list. This setup resolves versioned chapter directories and stages them for compilation.

How does chapter staging handle empty threads or chapters below readiness thresholds?

Chapter staging handles incomplete threads through graceful degradation, generating placeholder chapters and warnings instead of blocking the build. This ensures compilation continues even when chapter readiness thresholds are not met.

Does the book compilation process report the lifecycle state and review score of each chapter?

Yes, book compilation generates a BOOK_REPORT.md detailing each thread's resolved version, lifecycle state, review score, and audit status. This convergence reporting tracks the compilation progress of all staged chapters.

Can I use two-pass XeLaTeX compilation for collaborative document workflows with versioned directories?

Yes, two-pass XeLaTeX compilation supports collaborative document workflows by resolving the latest version from versioned chapter directories. It stages these versions into a master document and produces a final book.pdf deliverable.

What is the best way to track convergence progress across independent chapter threads during book assembly?

The best way to track convergence progress is by reviewing the generated BOOK_REPORT.md, which details the resolved version, lifecycle state, and audit status of each chapter thread after assembling the compiled book.