pipeline-conductor

Chain four Forge Harness verification pipelines into a gated sequential sweep.

7|Updated May 26, 2026
One-click install
npx skills add https://github.com/chrono-meta/forge-harness --skill pipeline-conductor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-conductor
Source: https://github.com/chrono-meta/forge-harness/tree/main/plugins/fh-meta/skills/pipeline-conductor
Command: npx skills add https://github.com/chrono-meta/forge-harness --skill pipeline-conductor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The four core Forge Harness verification pipelines (harvest-loop, steel-quench, phantom-quench, sim-conductor) are designed to run independently with no automatic handoff between steps. Running them manually loses critical inter-step signal, such as a FAIL in the adversarial verification step not blocking the subsequent phantom claim check, leading to incomplete or misleading verification results.

Core Features & Use Cases

  • Gated Sequential Execution: Automatically chains the four verification pipelines so each step's verdict controls whether the next step runs, eliminating manual coordination and missed signal.
  • Flexible Execution Modes: Supports --full (complete 4-step sweep), --quick (fast adversarial + phantom check), and --no-sim (skip simulation step) modes to match different verification needs, from quick iteration checks to full pre-release gates.
  • Aggregated Reporting & Resume: Compiles all findings into a single structured report with clear pass/fail/pending status, and supports resuming from failed steps without re-running already completed work.
  • Use Case: Before merging a pull request to a shared forge-harness project, run a full pipeline sweep to catch design flaws, ungrounded claims, and simulation issues in one go, rather than running each verification tool separately and manually tracking results.

Quick Start

Use the pipeline-conductor skill to run a full end-to-end verification sweep of your forge-harness project before opening a pull request.

Frequently Asked Questions about pipeline-conductor

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

FAQPage Schema
How do I chain multiple verification pipelines into a single gated sweep?

A gated sequential sweep automatically chains verification pipelines so each step's pass/fail verdict controls whether the next step runs, eliminating manual coordination and preventing misleading results from missed inter-step signals.

How do I run a pre-release quality gate check for ungrounded claims and design flaws?

Run a pre-release quality gate by executing a full verification sweep that aggregates adversarial testing, phantom claim detection, and simulation findings into a single structured verdict report, ensuring no flawed code reaches release.

Can I skip simulation during a verification pipeline run for faster iteration?

Yes, you can skip simulation during a verification pipeline run by using the simulation-optional execution mode. This performs a quick adversarial and phantom check without the computational overhead of full simulations.

What is the best way to resume a failed verification pipeline without re-running completed steps?

The best way to resume a failed verification pipeline is using a conductor with built-in resume capability. It restarts execution directly from the failed step, preserving already completed work and avoiding redundant processing.

Why does a failed adversarial testing step not block subsequent phantom claim checks?

A failed adversarial testing step fails to block subsequent checks when verification pipelines run independently without automatic handoff. Without a gated sequential sweep, critical inter-step signals are lost, leading to incomplete verification.