بنقرة واحدة
pipeline
Configurable pipeline orchestrator for sequencing stages
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Configurable pipeline orchestrator for sequencing stages
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Diagnose and fix oh-my-qwencode installation issues
Guide on using oh-my-qwencode plugin
Run deep investigation of architecture, bugs, performance issues, or dependencies and return structured findings with file:line evidence. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs root cause analysis before making changes. Routes to architect agent or Qwen Code MCP for thorough cross-file reasoning.
Ask Claude via local CLI and capture a reusable artifact
Ask Gemini via local CLI and capture a reusable artifact
Full autonomous execution from idea to working code
| name | pipeline |
| description | Configurable pipeline orchestrator for sequencing stages |
$pipeline is the configurable pipeline orchestrator for OMQ. It sequences stages
through a uniform PipelineStage interface, with state persistence and resume support.
The canonical OMQ pipeline sequences:
RALPLAN (consensus planning) -> team-exec (Qwen Code workers) -> ralph-verify (architect verification)
Pipeline parameters are configurable per run:
| Parameter | Default | Description |
|---|---|---|
maxRalphIterations | 10 | Ralph verification iteration ceiling |
workerCount | 2 | Number of Qwen Code team workers |
agentType | executor | Agent type for team workers |
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.
prd-*.md and test-spec-*.md planning artifacts already exist, and carries any deep-interview-*.md spec paths forward for traceability.Pipeline state persists via the ModeState system at .omq/state/pipeline-state.json.
The HUD renders pipeline phase automatically. Resume is supported from the last incomplete stage.
state_write({mode: "pipeline", active: true, current_phase: "stage:ralplan"})state_write({mode: "pipeline", current_phase: "stage:<name>"})state_write({mode: "pipeline", active: false, current_phase: "complete"})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);