pipeline

Orchestrate an end-to-end squad workflow with user gate checkpoints.

4|3|Updated May 2, 2026
One-click install
npx skills add https://github.com/ggemba/squad-mcp --skill pipeline-ggemba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/ggemba/squad-mcp/tree/main/skills/pipeline
Command: npx skills add https://github.com/ggemba/squad-mcp --skill pipeline-ggemba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The pipeline removes the friction of running multiple squad steps one-by-one by chaining them into a single end-to-end execution flow with clear user decision points.

Core Features & Use Cases

  • Cradle-to-grave orchestration: automatically chains brainstorming, plan hardening, tasking, next-task selection, implementation, and review into one guided sequence.
  • Explicit gate control: pauses at phase boundaries for proceed/adjust/skip/exit decisions, preventing silent advancement while still automating the workflow between gates.
  • Resume across sessions: persists minimal per-feature progress in .squad/pipeline-state.json so you can continue after context compaction or a closed session.
  • Inner loop per task: repeats next → implement → review until the backlog is exhausted, using the next sub-skill as source of truth for remaining tasks.

Quick Start

Trigger the full flow by asking: “Run the full squad pipeline for a feature: <feature description>”.

Frequently Asked Questions about pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate an end-to-end agent workflow for feature delivery?

You can orchestrate an end-to-end agent workflow by chaining brainstorming, plan hardening, tasking, implementation, and code review into a single sequence, pausing at explicit user gate checkpoints between phases for proceed or adjust decisions.

Can I resume an agent pipeline after closing a session or hitting context limits?

Yes, you can resume an agent pipeline after context compaction or a closed session because the workflow persists minimal per-feature progress in a `.squad/pipeline-state.json` file, allowing you to continue exactly where you left off.

What is the best way to automate task decomposition and implementation planning?

Automating task decomposition and implementation planning is best handled by an orchestrated pipeline that creates a task backlog and repeats an inner loop of next-task selection, implementation, and review until the backlog is exhausted.

How do I prevent silent advancement during automated workflow orchestration?

To prevent silent advancement during workflow orchestration, the pipeline pauses at phase boundaries, requiring explicit user gate control to decide whether to proceed, adjust, skip, or exit before automating the workflow to the next phase.

Do I need specific MCP tools to run a squad pipeline for code review and implementation?

Running a squad pipeline for code review and implementation requires sequencing via the Skill tool and utilizing MCP tools, but it does not require external dependencies, as it manages its own inner loop per task.