pipeline-overview

Explain the unfoldingWord BP pipeline and map stages to Skill.md paths.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Pipeline Overview provides a concise reference that explains the unfoldingWord Book Package pipeline, the nine stages, and which skill handles each stage, so users can quickly identify the right tool and workflow.

Core Features & Use Cases

  • Nine-stage pipeline mapping: describes each stage, its responsible skill, and how data flows from USFM to Door43 insertion.
  • Orchestrator guidance: clarifies end-to-end vs partial pipelines (makeBP, initial-pipeline, post-edit-review).
  • Common workflows reference: gives example prompts and how to chain skills for typical tasks such as generating ULT, identifying issues, aligning, and pushing to Door43.

Quick Start

Ask for an overview of the pipeline by stage or request "which skill handles the ULT generation for a chapter," and you'll receive the mapping and recommended actions.

Frequently Asked Questions about pipeline-overview

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

FAQPage Schema
What is the unfoldingWord Book Package pipeline and how does it work?

The Book Package pipeline is a nine-stage workflow that processes data from USFM input to Door43 insertion, with each stage mapped to a specific skill responsible for data transformation and orchestration.

How do I identify which skill handles a specific stage in the BP pipeline?

To identify the correct skill, reference the pipeline overview mapping, which lists the exact Skill.md paths and stage names for all nine stages to pinpoint the handler for tasks like ULT generation.

What is the difference between end-to-end and partial workflows in pipeline orchestration?

End-to-end workflows execute the full nine-stage sequence, while partial workflows like makeBP, initial-pipeline, and post-edit-review run isolated stage subsets to target specific processing tasks.

How do I chain skills together for common workflows like generating and aligning a ULT?

You chain skills by following the example prompts provided in the overview, which map out the sequence of stages needed for typical tasks like generating ULT, identifying issues, aligning, and pushing to Door43.

Do I need any specific dependencies or components to run the BP pipeline orchestration?

No specific dependencies or components are required to understand the orchestration, as the pipeline overview operates without external dependencies to map stages to their respective skills.