# Decide Pipelines

> When to use Laravel Pipelines vs sequential calls. Flow decisions.

- Skill: `attac-t/decide-pipelines` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add attac-t/decide-pipelines`
- Raw SKILL.md: https://api.skillmd.com/api/skills/attac-t/decide-pipelines/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: attac-t (https://skillmd.com/u/attac-t)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/attac-t/decide-pipelines

---


# Skill: Pipelines

> "Pipelines are for transformations. Actions are for operations."

## The Decision

**Use Pipeline when:**
- Data flows through sequential transformations
- Steps are interchangeable/configurable
- Each step enriches the same payload
- 3+ steps in sequence

**Use Sequential Calls when:**
- Steps have strong dependencies on each other
- Control flow (if/else) needed between steps
- Less than 3 steps
- Steps don't share a common payload

## The Heuristic

Ask: *"Am I transforming a payload, or orchestrating operations?"*

- **Transforming** → Pipeline
- **Orchestrating** → Action composition

## The Quick Test

| Ask Yourself                     | Answer | Use      |
|----------------------------------|--------|----------|
| 3+ sequential steps?             | Yes    | Pipeline |
| Steps reorderable?               | Yes    | Pipeline |
| Needs if/else between steps?     | Yes    | Actions  |
| Steps need each other's methods? | Yes    | Actions  |

## Real-World Examples

For concrete examples, see [examples.md](examples.md).