Skip to main content

What is Pipeline Kit

Pipeline Kit is a portable operating model plus a Python installer for coding agents. It ships two kits. You pick one per project at init.

KitWhat you installHow work runs
Kit mode (default)The markdown pack → .pipeline/IDE run-workflow + loader allowlist
Orchestrator modeThe Python engine in the wheelpipeline-kit run / approve / resume

Same first-party workflow names either way: ask, feature-development, Jira story/epic/bug. The pack is not tied to a product, a language, or an editor.

Full comparison: Two kits — pack and orchestrator.

:::info Handbook vs this site This documentation site is the guided product manual. After pipeline-kit init, the same adaptation contract is copied to .pipeline/docs/CUSTOMER-GUIDE.md in the target repo. Keep that file as the in-repo handbook; use these pages to learn the product. :::

What you take where​

You shipYou change per engagement
The kit (installer + bundled pack)AGENTS.md, .pipeline/config.json, local-deploy and test runbooks

What lands after install​

Kit mode (default):

PathRole
.pipeline/Workflows, skills, agent briefs, rules, wiki, loader, hooks
.pipeline/config.jsonThis engagement: chains, tracker, verify, deploy
.pipeline/docs/CUSTOMER-GUIDE.mdCopied handbook
.pipeline/docs/OBSERVABILITY.mdAgent-run observability handbook
.cursor/skills/run-workflow/ (or .claude / .github)The only IDE-discovered skill

Specialist briefs stay under .pipeline/ so the IDE does not auto-load them. The parent reads only the allowlist from the loader.

Orchestrator mode (--mode orchestrator) does not copy agents/, skills/, loader/, or workflows/. The chain lives in the wheel. You still get config.json, docs, hooks, and features/{slug}/.

Shipped workflows​

NameWhen it runs
askQuestion about this repo (how / what / why / explain). No Task chain.
feature-developmentProduct work from chat (“add”, “fix”, “change”, “implement”).
jira-story / jira-epic / jira-bugTracker issue key, if Jira intake is enabled.
github-story / github-epic / github-bugGitHub issue or PR, if GitHub intake is enabled.
test-knowledge-bootstrapOne-time QA overlay bootstrap. Not the feature ladder.

Opt-in extras — knowledge, plugins, agent-run observability — are documented under Capabilities. pipeline-kit init does not turn them on.

How the source repo is grouped: Repository layout.

Requirements​

Python 3.11+ and the cryptography package (installed with pipeline-kit). Optional plugins (Graphify, Archify) and bundled observability (Langfuse keys) are separate.

Next​

  1. Two kits — pack and orchestrator
  2. Problems it solves
  3. How it works
  4. Install the CLI