Extensions
A new customer process is an extension, not a new platform. The contract depends on which kit the project was initialized with — pack (kit mode) or orchestrator.
extensions/
kit/ markdown pack (skill + JSON + config)
orchestrator/ Python graphs (pipeline_extensions/)
Kit mode
After pipeline-kit init:
.pipeline/skills/{name}/SKILL.md.pipeline/workflows/{name}.jsonallowlistsworkflows.{name}in.pipeline/config.json- Optional agent brief on that step’s allowlist
- Optional receptionist row in
skills/orchestration/SKILL.md
python3 .pipeline/loader/load_workflow.py --workflow {name} --step parent --slug try-{name}
To ship a first-party workflow in this repository, edit kit/pipeline/ the same way, then pipeline-kit update in customer apps. Follow DOCUMENT-STANDARD.
Step-by-step: Add a workflow.
Orchestrator mode
Associates add Python graphs. Kit mode never imports these files.
pipeline-kit workflows --scaffold my-review
That writes pipeline_extensions/my_review.py plus a brief. Do not reuse a first-party name.
Copy-ready examples in the kit clone (security-review, ci-audit, dependency-audit, accessibility-review):
cp -R extensions/orchestrator/pipeline_extensions /path/to/your-app/
pipeline-kit init --mode orchestrator --ide cursor
pipeline-kit workflows
pipeline-kit run --slug pci-sample --workflow security-review --runner fake \
--request "review auth, secrets, and CSRF on the checkout routes"
You can also register a pipeline_kit.workflows setuptools entry point. The public import is:
from pipeline_orchestrator.graph import AgentStep, SignoffGate, WorkflowSpec
What not to mix
| Do | Do not |
|---|---|
Add a kit workflow in .pipeline/ (or kit/pipeline/ to ship it) | Expect pipeline_extensions/ to run in kit mode |
Add an orchestrator workflow in pipeline_extensions/ | Expect the markdown loader to run that graph |
| Keep first-party names reserved | Replace feature-development with a custom file of the same name |