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".

AI & Automation 8 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
32
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
2 months ago
Last Updated
today
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

full-pipeline

Orchestrates the user's full end-to-end workflow in order — gstack office-hours, autoplan, autoresearch-plan, superpowers writing-plans and subagent-driven-development, autoresearch-impl, code-review, and qa — invoking each skill in sequence and handing its output forward as the next step's input. At two fixed checkpoints (after the plan is locked, and after implementation lands) it judges whether the change touches database schema and if so invokes supabase:supabase-postgres-best-practices before continuing. Use whenever the user wants to "run the whole pipeline", "go from idea to shipped", "do the full flow", or asks Claude Code to chain their office-hours → autoplan → superpowers → qa workflow automatically instead of invoking each skill by hand.

0 Updated 4 days ago
darkstar1227
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.)

8 Updated today
chrono-meta
Code & Development Listed

devlynresolve

Hands-free pipeline for any coding task — bug fix, feature, refactor, debug, modify, PR review. Free-form goal or formal spec input. Plan → Implement → Build-gate → Cleanup → Verify (fresh subagent, findings-only). Mechanical-first verification; Verify dual-judge is default-when-available. Use when the user says "resolve this", "fix this", "implement this", "refactor this", "debug this", "review this PR", or wants hands-off completion.

2 Updated today
fysoul17