Setup CI

Collect pipeline requirements from the user, inspect the repository, and produce CI configuration that matches the chosen platform and quality bar.

Intake (required before pipeline work)

Collect the four areas below before generating any CI configuration. Skip an area only when it is already explicit in the user's request or conversation.

If the environment provides an interactive question tool, collect the full intake in one form with at most 4 related questions; otherwise ask in chat. Question rules:

• Use choice questions for fixed decisions; use multi-select where several answers can apply (artifacts, quality gates).
• Do not turn multi-answer decisions into freeform questions; collect extra paths, tool names, and details in a separate freeform question.
• Ask no more than 4 questions total unless a prior answer is too vague to proceed safely.
• Use repository inspection, not questions, for facts discoverable in files.
• Do not read secrets, .env, credentials, kubeconfigs, or auth stores to fill gaps; ask the user for sanitized placeholders or secret names instead.

1. CI platform

Which CI flavor to target: