pipeline-conductor
SolidChains 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".
Install
Quality Score: 83/100
Skill Content
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
pipeline
Use when the user asks to take a substantial feature from an initial idea through implementation in one mostly autonomous run.
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).
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.)