Skill Claude

Pipeline State

pipeline-state/

2 views 0 downloads

A small file-backed handoff bus for multi-agent runs: each phase records its outputs and evidence paths, so later phases look them up instead of re-pasting them. Survives context compression.

Pipeline State: Brain Lab skill for Claude Code

A durable, file-backed handoff bus so multi-agent runs pass references, not giant inlined dumps.

Why use it

Phase 4 re-pastes everything phase 3 produced, and the context window pays for it twice.
A long run gets compressed and the earlier phases' outputs are simply gone.
"What did the last phase actually produce?" has no machine-readable answer.

What it does

One per-run, git-ignored JSON file holding the run's variables, each phase's outputs, and paths to its evidence.
Read-on-START / write-on-COMPLETION protocol: pull your inputs by lookup, record your outputs as fields + PATHS.
A small shell script, init / set / append / get / clear, plus the state schema.
Coexists with your committed reports: it references them, it never replaces them.

Benefits

Small prompts, long runs. Handoffs become lookups instead of re-pasted dumps.
Survives context compression: nothing from phase 2 is lost by phase 8.
Gates you can trust. The orchestrator validates from evidence, not from a summary.
One script, any pipeline. No service, no database, no dependencies.

Install

Download this skill and copy the pipeline-state folder to .claude/skills/pipeline-state/ in your project, or to ~/.claude/skills/pipeline-state/ to use it in every project. Claude Code finds it on its own; you can also call it with /pipeline-state.

Part of the Context Engineering bundle. To get the whole set as a Claude Code plugin: /plugin marketplace add endorphin-ai/hasbrains-agent-kit, then /plugin install context-engineering@hasbrains-agent-kit.

Source: endorphin-ai/hasbrains-agent-kit. License: MIT.

Files (7)

# pipeline-state

> A durable, file-backed handoff bus so multi-agent runs pass references — not giant inlined dumps.

**Plugin:** `context-engineering` — `/plugin install context-engineering@hasbrains-agent-kit`

## Why use it

- Phase 4 re-pastes everything phase 3 produced, and the context window pays for it twice.
- A long run gets compressed and the earlier phases' outputs are simply gone.
- "What did the last phase actually produce?" has no machine-readable answer.

## What it does

- One per-run, git-ignored JSON file holding the run's variables, each phase's outputs, and paths to its evidence.
- Read-on-START / write-on-COMPLETION protocol: pull your inputs by lookup, record your outputs as fields + PATHS.
- A small shell script — `init` / `set` / `append` / `get` / `clear` — plus the state schema.
- Coexists with your committed reports: it references them, it never replaces them.

## Benefits

- **Small prompts, long runs.** Handoffs become lookups instead of re-pasted dumps.
- **Survives context compression** — nothing from phase 2 is lost by phase 8.
- **Gates you can trust.** The orchestrator validates from evidence, not from a summary.
- **One script, any pipeline.** No service, no database, no dependencies.

---

Made by **HasBrains** — https://hasbrains.com/