run-pipeline

Automate an agent pipeline by loading named stage skills from .harness/skills and enforcing mechanical quality gates after each stage. This standardizes failure handling and improves reliability across structured workflows. Human gates require explicit prompts and approvals in conversation.

A human gate in a multi-stage workflow pipeline is an explicit approval prompt in the conversation that halts execution until manually approved. This ensures mechanical quality checks pass and human oversight is applied before proceeding to the next stage.

Track pipeline failures and progress by using .harness files for memory tracking and failure logging. The pipeline automatically records progress, failures, and improvements in memory, with optional Notion integration for external tracking.

Yes, this pipeline orchestration is designed for projects that require structured stage workflows, mechanical quality checks, and human gate approvals across multiple stages. Scaffold the harness with /harness and run the pipeline to execute Stage 1.

The best way to enforce quality checks between agent pipeline stages is to apply mechanical quality gates automatically after each stage skill executes. This ensures artifact verification and gate enforcement happen consistently before downstream stages run.

Pipeline execution halts between stages when a human gate requires explicit approval in the conversation. The pipeline enforces these gates mechanically after each stage to ensure quality checks pass before proceeding to subsequent workflow steps.