pipeline-conductor

Solid

Chains the four core FH verification pipelines (harvest-loop → steel-quench → phantom-quench → sim-conductor) into a single gated sweep. Accepts a scope (single skill, specific asset, full harness) and aggregates results into one structured report. Supports --quick mode (steps 2+3 only) and --full mode (all four steps). Triggered by "run the full pipeline", "chain all verifications", "end-to-end sweep", "pipeline-conductor", or "verify everything".

Data & Documents 16 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
41
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# pipeline-conductor — Chained Verification Sweep Chains the four standalone FH verification pipelines into a gated sequence. Each step receives the previous step's verdict before proceeding. Aggregates all findings into a single structured report at the end. The gap this closes: harvest-loop, steel-quench, phantom-quench, and sim-conductor are each invocable independently but have no automatic hand-off between them. Running them sequentially by hand loses inter-step signal — a FAIL in step 2 should block step 3 rather than silently continuing. pipeline-conductor enforces that ordering. ## Triggers - `/pipeline-conductor` - "Run the full verification pipeline", "chain all four verifications" - "End-to-end sweep before I push", "verify everything at once" - "I want to run all the checks in order", "do a full harness review" - "Run quench then grounding then sim", "chain the pipelines" - "Full pipeline on this skill", "sweep this asset before release" > **Disambiguation**: "run the pipeline" alone may trigger harvest-loop (which uses identical phrasing). Prefer "run pipeline-conductor" or "chain all verifications" for unambiguous activation. ## Modes | Flag | Steps run | When to use | |---|---|---| | `--full` (default) | Steps 1 → 2 → 3 → 4 | Complete verification sweep | | `--quick` | Steps 2 → 3 only | Fast adversarial + phantom check; skip knowledge loop and simulation | | `--no-sim` | Steps 1 → 2 → 3 | Skip sim-conductor (e.g., no sim environment available) | **Mode...

Details

Author
chrono-meta
Repository
chrono-meta/forge-harness
Created
4 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

pipeline

Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.

2 Updated 2 days ago
kardebadas
Data & Documents Listed

conductor

(v2026-08-05.1) Execute a run-list document — pipeline stage 3 of design-swarm → run-list → conductor. The conductor reads the run-list tolerantly (no compiler, no sidecar), front-loads ALL operator input into one decide-once brief, then runs the rows: tiered workers dispatched per row, every row verified by a mechanical probe before it ticks, checkpoints kept in the run-list itself, and anything canonical/physical/unknown parked to a plain-English return board. Trigger on: 'execute the run-list', 'run the run-list', 'resume the run', 'conductor session on <run-list', or any ask to actually run or resume a staged run-list. Do NOT trigger for planning a build (that is run-list) or designing one (that is design-swarm).

1 Updated 1 months ago
fastedd27
AI & Automation Solid

harvest-loop

An 8-step self-evolution pipeline that runs after field sessions end (field-harvest → contention-layer → challenger + persona-innovator → synthesizer → Critic agent → harness-doctor → verify-bidirectional → curator), absorbing session learnings back into the FH ecosystem. Runs automatically at session end in the main dev environment; proposes execution first for external users. Triggered by "session harvest", "learning absorption", "fh evolution", or "harvest-loop". (The phrase "run the pipeline" is ceded to pipeline-conductor — use that for end-to-end verification sweeps.)

16 Updated today
chrono-meta