template-pipeline

Numbered pipeline stage scripts in scripts/pipeline/.

When to use

Load this skill when you need to:

• Run or debug a specific pipeline stage
• Add a new stage script
• Understand the stage → infrastructure module mapping
• Work with opt-in stages (08 connector_search, 09 provenance_record, 10 research_workflow)

Stage inventory

| Script | Infrastructure module | |--------|-----------------------| | stage_00_setup.py | infrastructure.core.runtime.environment | | stage_01_test.py | infrastructure.core.testing | | stage_02_analysis.py | infrastructure.core.analysis | | stage_03_render.py | infrastructure.rendering | | stage_04_validate.py | infrastructure.validation | | stage_05_copy.py | infrastructure.core.files | | stage_06_llm_review.py | infrastructure.llm | | stage_07_executive_report.py | infrastructure.reporting | | stage_08_connector_search.py | infrastructure.search.connectors (opt-in) | | stage_09_provenance_record.py | infrastructure.provenance (opt-in) | | stage_10_research_workflow.py | infrastructure.research.ResearchWorkflow (opt-in) | | stage_11_ebook.py | infrastructure.publishing.ebook | | stage_12_metadata.py | infrastructure.publishing.metadata |

Bootstrap pattern

python
sys.path.insert(0, str(Path(__file__).resolve().parents[2]))
from scripts import ensure_repo_root_on_path
ensure_repo_root_on_path()

Pitfalls

• Always use parents[2] (not parent.parent) — scripts live at depth 3.
• Opt-in stages (08–10) should exit 2 when backend is absent, not 1.
• Never add business logic to stage scripts — keep them thin orchestrators.