makeBP

Orchestrate end-to-end Book Package generation from ULT through repo-insert.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/unfoldingWord/bp-assistant-skills --skill makebp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: makeBP
Source: https://github.com/unfoldingWord/bp-assistant-skills/tree/main/.claude/skills/makeBP
Command: npx skills add https://github.com/unfoldingWord/bp-assistant-skills --skill makebp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end generation of a Book Package for a single chapter, coordinating all pipeline stages from ULT through repo-insert to deliver a complete BP ready for publication.

Core Features & Use Cases

  • End-to-end BP generation for a chapter, coordinating multiple phases (ULT, UST, chapter intro, alignments, TN, and TQ) and performing repo insertions.
  • Task-subagent orchestration: each phase runs as a separate Task subagent with dedicated models and deterministic steps.
  • Automated publishing: pushes to Door43 repos and creates PRs as part of an integrated workflow.

Quick Start

Ask Claude to initiate a full BP build for a given book and chapter.

Frequently Asked Questions about makeBP

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

FAQPage Schema
How do I automate end-to-end Book Package generation for a single chapter?

Book Package generation is automated by orchestrating multiple pipeline stages from ULT through repo-insert. A task-based model coordinates dedicated subagents to produce ULT, UST, alignments, TN notes, and TQ content for a complete chapter.

What is a Book Package pipeline and how does chapter orchestration work?

A Book Package pipeline coordinates sequential phases including ULT, UST, chapter intro, alignments, TN, and TQ generation. Chapter orchestration uses explicit phase handoffs and parameter normalization to pass content between separate Task subagents.

How do I push generated Bible translation content to Door43 repositories automatically?

Generated Bible translation content is pushed to Door43 repositories automatically through the pipeline. The workflow performs automated repo insertions and creates PRs to staging branches after all chapter content phases complete successfully.

Can I generate ULT and UST translations together with alignments and translation notes in one workflow?

ULT and UST translations, alignments, and translation notes are generated together in one integrated workflow. The orchestration model assigns each resource type to a separate subagent with dedicated models, coordinating all outputs for the target chapter.

Do I need to manually create pull requests when publishing a chapter Book Package to Door43?

Manual pull request creation is not needed when publishing a chapter Book Package to Door43. The pipeline includes automated publishing that handles repo pushes and PR creation to staging branches as part of the integrated workflow.

What are the limitations of automated chapter Book Package orchestration?

Automated chapter Book Package orchestration is limited to processing one chapter at a time and depends on successful completion of all sequential phases. If any subagent phase fails during the pipeline, downstream stages like repo-insert may not execute properly.