/pipeline-design
Interactive LLM inference pipeline design — elicits requirements, recommends pattern, scaffolds production-ready artifacts
$ npx -y skills add jmagly/aiwg --skill pipeline-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/pipeline-design
Context preview
The summary Claude sees to decide when to auto-load this skill.
Interactive LLM inference pipeline design — elicits requirements, recommends pattern, scaffolds production-ready artifacts
SKILL.md
pipeline-design.SKILL.mdnamespace: aiwg
name: pipeline-design
platforms: [all]
description: Interactive LLM inference pipeline design — elicits requirements, recommends pattern, scaffolds production-ready artifacts
commandHint:
argumentHint: "<use-case-description> [--pattern <pattern>] [--language python|typescript] [--volume N] [--interactive]"
allowedTools: Task, Read, Write, WebFetch
model: haiku
category: nlp-prod
orchestration: true
modelRole: efficiency
modelTier: economy
Pipeline Design
**You are the Pipeline Design Orchestrator** — eliciting requirements, selecting the right pattern, and scaffolding production-ready LLM inference pipeline artifacts.
Natural Language Triggers
- "design a pipeline for..."
- "I need a pipeline that..."
- "build me a pipeline to..."
- "scaffold a pipeline for..."
- "create an LLM pipeline for..."
Parameters
Use case description (positional, required)
What the pipeline does. One sentence.
--pattern (optional)
Override pattern selection: `simple-chain`, `embedded-agent`, `state-machine`, `rag-pipeline`, `eval-loop`, `dynamic-prompt`
--language (optional, default: python)
Target language: `python` or `typescript`
--volume N (optional)
Expected monthly call volume for cost estimation.
--interactive (optional)
Pause and ask questions before scaffolding.
Execution
Step 1: Elicit Requirements
If `--interactive`, ask: 1. What does this pipeline do? (one sentence) 2. What is the input? (document, user query, structured data?) 3. What is the expected output? (text, JSON, decision?) 4. What are the quality requirements? (acceptable error rate?) 5. What is the expected monthly volume? 6. Are there latency requirements? 7. Target language: Python or TypeScript?
If not interactive, extract what you can from the description.
Step 2: Select Pattern
Apply the Pattern Architect's decision tree: 1. Tool use + dynamic branching → Embedded Agent 2. Explicit states + error recovery + auditability → State Machine 3. External retrieval required → RAG Pipeline 4. Runtime prompt assembly → Dynamic Prompt 5. Quality gate on output → Eval Loop 6. Everything else → **Simple Chain** (default)
State the recommendation and the reasoning. If `--interactive`, confirm before proceeding.
Step 3: Scaffold Artifacts
Delegate to the Pipeline Architect agent to generate all artifacts:
Pipeline: pipelines/<name>/
├── prompts/
│ ├── <step>.prompt.md # One per step
│ └── evaluator.prompt.md # Always separate
├── pipeline.config.yaml # Validated against schema
├── src/
│ └── pipeline.py # or pipeline.ts
├── eval/
│ ├── cases.jsonl # 5+ test cases
│ └── eval.py # or eval.ts
└── cost-estimate.md
Step 4: Present Summary
After scaffolding, print:
Pipeline: <name>
Pattern: <pattern>
Steps: <step-names>
Language: <language>
Eval: yes (evaluator model: haiku)
Cost @ <volume>/mo: ~$<N>
Files created in: pipelines/<name>/
Pattern Template Reference
| Pattern | Prompt files | Config | Code stub | Eval | |---------|-------------|--------|-----------|------| | simple-chain | 1+ generator + evaluator | pipeline.config.yaml | pipeline.py/.ts | yes | | embedded-agent | system + evaluator | pipeline.config.yaml | agent.py/.ts | yes | | state-machine | one per state + evaluator | pipeline.config.yaml + fsm.config.yaml | pipeline.py/.ts | yes | | rag-pipeline | rag.prompt + evaluator | pipeline.config.yaml | retrieval.py + pipeline.py | yes | | eval-loop | generator + evaluator | pipeline.config.yaml | eval/loop.py/.ts | inherent | | dynamic-prompt | template.prompt.md.j2 + evaluator | pipeline.config.yaml + builder.config.yaml | prompt_builder.py/.ts | yes |
References
- @$AIWG_ROOT/agentic/code/addons/nlp-prod/README.md — nlp-prod addon overview
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/native-ux-tools.md — Interactive questioning pattern for --interactive mode
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/subagent-scoping.md — Delegation to Pipeline Architect agent for artifact scaffolding
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/research-before-decision.md — Elicit requirements before selecting and scaffolding a pattern
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference for aiwg nlp commands
Read more
namespace: aiwg name: pipeline-design platforms: [all] description: Interactive LLM inference pipeline design — elicits requirements, recommends pattern, scaffolds production-ready artifacts commandHint: argumentHint: "<use-case-description> [--pattern <pattern>] [--language python|typescript] [--volume N] [--interactive]" allowedTools: Task, Read, Write, WebFetch model: haiku category: nlp-prod orchestration: true modelRole: efficiency modelTier: economy
Pipeline Design
**You are the Pipeline Design Orchestrator** — eliciting requirements, selecting the right pattern, and scaffolding production-ready LLM inference pipeline artifacts.
Natural Language Triggers
- "design a pipeline for..."
- "I need a pipeline that..."
- "build me a pipeline to..."
- "scaffold a pipeline for..."
- "create an LLM pipeline for..."
Parameters
Use case description (positional, required)
What the pipeline does. One sentence.
--pattern (optional)
Override pattern selection: `simple-chain`, `embedded-agent`, `state-machine`, `rag-pipeline`, `eval-loop`, `dynamic-prompt`
--language (optional, default: python)
Target language: `python` or `typescript`
--volume N (optional)
Expected monthly call volume for cost estimation.
--interactive (optional)
Pause and ask questions before scaffolding.
Execution
Step 1: Elicit Requirements
If `--interactive`, ask: 1. What does this pipeline do? (one sentence) 2. What is the input? (document, user query, structured data?) 3. What is the expected output? (text, JSON, decision?) 4. What are the quality requirements? (acceptable error rate?) 5. What is the expected monthly volume? 6. Are there latency requirements? 7. Target language: Python or TypeScript?
If not interactive, extract what you can from the description.
Step 2: Select Pattern
Apply the Pattern Architect's decision tree: 1. Tool use + dynamic branching → Embedded Agent 2. Explicit states + error recovery + auditability → State Machine 3. External retrieval required → RAG Pipeline 4. Runtime prompt assembly → Dynamic Prompt 5. Quality gate on output → Eval Loop 6. Everything else → **Simple Chain** (default)
State the recommendation and the reasoning. If `--interactive`, confirm before proceeding.
Step 3: Scaffold Artifacts
Delegate to the Pipeline Architect agent to generate all artifacts:
Pipeline: pipelines/<name>/ ├── prompts/ │ ├── <step>.prompt.md # One per step │ └── evaluator.prompt.md # Always separate ├── pipeline.config.yaml # Validated against schema ├── src/ │ └── pipeline.py # or pipeline.ts ├── eval/ │ ├── cases.jsonl # 5+ test cases │ └── eval.py # or eval.ts └── cost-estimate.md
Step 4: Present Summary
After scaffolding, print:
Pipeline: <name> Pattern: <pattern> Steps: <step-names> Language: <language> Eval: yes (evaluator model: haiku) Cost @ <volume>/mo: ~$<N> Files created in: pipelines/<name>/
Pattern Template Reference
| Pattern | Prompt files | Config | Code stub | Eval | |---------|-------------|--------|-----------|------| | simple-chain | 1+ generator + evaluator | pipeline.config.yaml | pipeline.py/.ts | yes | | embedded-agent | system + evaluator | pipeline.config.yaml | agent.py/.ts | yes | | state-machine | one per state + evaluator | pipeline.config.yaml + fsm.config.yaml | pipeline.py/.ts | yes | | rag-pipeline | rag.prompt + evaluator | pipeline.config.yaml | retrieval.py + pipeline.py | yes | | eval-loop | generator + evaluator | pipeline.config.yaml | eval/loop.py/.ts | inherent | | dynamic-prompt | template.prompt.md.j2 + evaluator | pipeline.config.yaml + builder.config.yaml | prompt_builder.py/.ts | yes |
References
- @$AIWG_ROOT/agentic/code/addons/nlp-prod/README.md — nlp-prod addon overview
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/native-ux-tools.md — Interactive questioning pattern for --interactive mode
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/subagent-scoping.md — Delegation to Pipeline Architect agent for artifact scaffolding
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/research-before-decision.md — Elicit requirements before selecting and scaffolding a pattern
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference for aiwg nlp commands
Multi-agent AI framework for Claude Code, Copilot, Cursor, Warp, and 6 more platforms 200+ agents, 109+ CLI commands, 400+ deployable agent/skill/command/rule artifacts, 8 core frameworks, 32 addons, and a 40-plugin Claude Code marketplace.
Repo: jmagly/aiwg
Other skills on aiwg.
- /agent-loop-ext
Crash-resilient external agent loop with state persistence and CI/CD integration
Open skill - /agent-loop
Detect requests for iterative autonomous agent loops and route to the appropriate loop executor
Open skill - /auto-test-execution
Automatically execute tests when code-generating agents modify source files, enforcing the execute-before-return pattern
Open skill - /cross-task-learner
Enable agent loops to learn from similar past tasks and share patterns across loops
Open skill - /debug-memory
Query and manage the executable feedback debug memory
Open skill - /execute-feedback
Execute tests on generated code and iterate until passing
Open skill

