Add a workflow
A new customer process should be a workflow, not a fork of the kit. There are two contracts — pick the mode the project was initialized with.
Kit mode (default)
- Write
.pipeline/skills/{name}/SKILL.md(plusassets/templates if needed). - Write
.pipeline/workflows/{name}.jsonwithcontext.parent.filesandcontext.steps.{agent}.files(relative paths from the project root,.pipeline/…prefix). - Add
workflows.{name}in.pipeline/config.json(source,chainorclasses,skips). An emptychainmeans parent-only (seeask). - Optional: add
.pipeline/agents/{role}.mdand list it on that step’s allowlist. - If the receptionist should auto-pick it, add one row to
.pipeline/skills/orchestration/SKILL.md(O1 / O3). - Activate and check the printed list:
python3 .pipeline/loader/load_workflow.py --workflow {name} --step parent --slug try-{name}
Confirm allowed_reads is the smallest set that step needs.
Follow DOCUMENT-STANDARD so the new markdown stays portable.
Kit-repo copy of this contract: extensions/kit/.
Orchestrator mode
--mode orchestrator does not use the markdown loader. Add a Python graph:
pipeline-kit workflows --scaffold my-review
That writes pipeline_extensions/my_review.py and a brief. Copy-ready examples (security review, CI audit, dependency audit, accessibility review) live in the kit clone at extensions/orchestrator/.
cp -R extensions/orchestrator/pipeline_extensions /path/to/your-app/
Do not reuse a first-party name. Kit mode never loads pipeline_extensions/.
Full comparison: Kit vs orchestrator, Extensions.