Skip to main content

Your first workflow

These steps assume kit mode (the default) — the project pack is installed and AGENTS.md routes to run-workflow. If you initialized with --mode orchestrator, skip to Orchestrator smoke test.

1. Ask (no Task chain)​

In the IDE, with the repo root open:

How does local deploy work in this repository?

Expect workflow ask. The parent runs the loader, reads the allowlist, and answers from the repo. It must not start PM → BA → developer.

Details: Ask workflow.

2. A small product change​

Add a small label change on the homepage.

Expect feature-development. The parent classifies micro / minor / feature before any specialist Task. A label tweak is usually micro: developer → tester (if policy) → devops → retro.

If the parent starts a full PRD for a label, stop and read change classes.

Details: Feature development.

3. Tracker key (only if Jira is on)​

If intake.jira.enabled is true and connection is set (mcp, cli, or api):

Work on ABC-123

Expect intake first, then jira-story, jira-epic, or jira-bug from the issue type. Do not paste the ticket body into chat to “save a step.”

4. GitHub issue (only if GitHub intake is on)​

If intake.github.enabled is true (pipeline-kit features enable github-intake):

Work on https://github.com/acme/app/issues/12

Expect intake first (gh by default), then github-story, github-epic, or github-bug. Bare #12 only works when intake.github.repo is set.

If nothing happens​

  1. Confirm the run-workflow skill is visible in the IDE.
  2. Confirm you opened the repo that contains .pipeline/ and the adapter folder.
  3. Run pipeline-kit doctor --ide cursor.
  4. Off-repo trivia (weather, news) must skip the loader — that is correct.

Orchestrator smoke test​

You initialized with --mode orchestrator. Do not wait for run-workflow to pick a chain.

pipeline-kit run --slug label-tweak --workflow feature-development --runner fake \
--request "Add a small label change on the homepage"
pipeline-kit status --slug label-tweak

--runner fake writes state under features/label-tweak/ without calling the Cursor SDK. A live run needs CURSOR_API_KEY and --request (or --request-file). Chat text is not inherited.

Details: Two kits, CLI — orchestrator.