agentleFS
lza6lza6/claw-code-tingfeng/skills/pipeline/SKILL.md

pipeline

Skill5 starsChanged 13 days agoMITView on GitHub

Configurable pipeline orchestrator for sequencing stages

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use follow-up, status and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • n24q02mSkill

    follow-up

    Find emails needing follow-up -- unanswered sent emails, flagged unreplied, draft contextual responses

    Also in 3 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 5 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 3 projects that use this

  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 3 projects that use this

  • dubwoahSkill

    ask

    Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every stage implements the PipelineStage interface:

    line 31

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Pipeline Skill

$pipeline is the configurable pipeline orchestrator for OMX. It sequences stages through a uniform PipelineStage interface, with state persistence and resume support.

Default Autopilot Pipeline

The canonical OMX pipeline sequences:

RALPLAN (consensus planning) -> team-exec (Codex CLI workers) -> ralph-verify (architect verification)

Configuration

Pipeline parameters are configurable per run:

ParameterDefaultDescription
maxRalphIterations10Ralph verification iteration ceiling
workerCount2Number of Codex CLI team workers
agentTypeexecutorAgent type for team workers

Stage Interface

Every stage implements the PipelineStage interface:

interface PipelineStage {
  readonly name: string;
  run(ctx: StageContext): Promise<StageResult>;
  canSkip?(ctx: StageContext): boolean;
}

Stages receive a StageContext with accumulated artifacts from prior stages and return a StageResult with status, artifacts, and duration.

Built-in Stages

  • ralplan: Consensus planning (planner + architect + critic). Skips only when both prd-*.md and test-spec-*.md planning artifacts already exist, and carries any deep-interview-*.md spec paths forward for traceability.
  • team-exec: Team execution via Codex CLI workers. Always the OMX execution backend.
  • ralph-verify: Ralph verification loop with configurable iteration count.

State Management

Pipeline state persists via the ModeState system at .omx/state/pipeline-state.json. The HUD renders pipeline phase automatically. Resume is supported from the last incomplete stage.

  • On start: state_write({mode: "pipeline", active: true, current_phase: "stage:ralplan"})
  • On stage transitions: state_write({mode: "pipeline", current_phase: "stage:<name>"})
  • On completion: state_write({mode: "pipeline", active: false, current_phase: "complete"})

API

import {
  runPipeline,
  createAutopilotPipelineConfig,
  createRalplanStage,
  createTeamExecStage,
  createRalphVerifyStage,
} from './pipeline/index.js';

const config = createAutopilotPipelineConfig('build feature X', {
  stages: [
    createRalplanStage(),
    createTeamExecStage({ workerCount: 3, agentType: 'executor' }),
    createRalphVerifyStage({ maxIterations: 15 }),
  ],
});

const result = await runPipeline(config);

Relationship to Other Modes

  • autopilot: Autopilot can use pipeline as its execution engine (v0.8+)
  • team: Pipeline delegates execution to team mode (Codex CLI workers)
  • ralph: Pipeline delegates verification to ralph (configurable iterations)
  • ralplan: Pipeline's first stage runs RALPLAN consensus planning

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.