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
- PeterPartridge/CooperativeAICodingtheir own version, first seen Nov 8, 2026
- Jakeschincariol/closer-skilltheir own version, first seen Nov 8, 2026
- Nucleify/Nucleifytheir own version, first seen Nov 2, 2026
- Jlosev/agent-skillstheir own version, first seen Oct 30, 2026
- okfriansyah-moh/agentic-workflowtheir own version, first seen Oct 25, 2026
- ClarvAI/job-search-hqtheir own version, first seen Oct 15, 2026
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.
n24q02mSkillfollow-up
Find emails needing follow-up -- unanswered sent emails, flagged unreplied, draft contextual responses
Also in 3 projects that use this
AnthropicSkillstatus
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
genomewalkerSkillresume
Resume a thread by loading its ~800-token context capsule
Also in 3 projects that use this
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 3 projects that use this
dubwoahSkillask
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
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- Yeachan-Heo/oh-my-codex★ 34ksame name
- H-mmer/pentest-agents★ 815same name
- spytensor/openmozi★ 215same name
- Nucleify/Nucleify★ 171same name
- akashgit/remote-factory★ 74same name
- boston-harness-group/remote-factory★ 74same name
- baekenough/oh-my-customcode★ 42same name
- Jakeschincariol/closer-skill★ 33same name
- Magerko/claude-code-skills★ 22same name
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
19 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository119 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibilitySkill
- frontend-designSkill
- python-background-jobsSkill
- python-executorSkill
- python-testing-patternsSkill
- seoSkill
- ai-slop-cleanerSkill
- analyzeSkill
- api-and-interface-designSkill
- ask-claudeSkill
- ask-geminiSkill
- autopilotSkill
- browser-testing-with-devtoolsSkill
- build-fixSkill
- cancelSkill
- ci-cd-and-automationSkill
- clawd-change-workflowSkill
- code-review-and-qualitySkill
- code-reviewSkill
- code-simplificationSkill
- configure-notificationsSkill
- context-engineeringSkill
- debugging-and-error-recoverySkill
- deep-interviewSkill
- deepsearchSkill
- deprecation-and-migrationSkill
- doctorSkill
- documentation-and-adrsSkill
- ecomodeSkill
- frontend-ui-engineeringSkill
- frontend-ui-uxSkill
- git-masterSkill
- git-workflow-and-versioningSkill
- helpSkill
- hudSkill
- idea-refineSkill
- incremental-implementationSkill
- intent_routerSkill
- keyword_registrySkill
- mode_stateSkill
- noteSkill
- omx-setupSkill
- performance-optimizationSkill
- pipeline_orchestratorSkill
- planning-and-task-breakdownSkill
- planSkill
- ralph-initSkill
- ralph_loopSkill
- ralphSkill
- ralplanSkill
- android-reverse-engineeringSkill
- api-securitySkill
- apk-reverseSkill
- attack-chainSkill
- binary-diffSkill
- browser-automationSkill
- browser-extension-reverseSkill
- The first 60 shown.
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
- Very specific: line 31
Every stage implements the PipelineStage interface:
“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.
Files
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:
| Parameter | Default | Description |
maxRalphIterations | 10 | Ralph verification iteration ceiling |
workerCount | 2 | Number of Codex CLI team workers |
agentType | executor | Agent 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-*.mdandtest-spec-*.mdplanning artifacts already exist, and carries anydeep-interview-*.mdspec 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
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
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.

