Skip to content
cliq Docs

Generate with Builder

The Builder uses an LLM to generate a complete team from a natural language description — workflow DAG, role prompts, gate checks, A2A metadata, everything.

Generate a team

Section titled “Generate a team”
Terminal window
mkdir blog-pipeline && cd blog-pipeline
cliq builder generate -m "Blog content pipeline with researcher, writer, editor, and quality gate"

The Builder produces a validated team and writes it directly into your current directory:

✓ Team 'blog-content-pipeline' created


  Path:   /Users/you/blog-pipeline
  Phases: 5
  Roles:  4


  Workflow:
    researcher [standard] (root)
    writer [standard] → depends on researcher
    editor [standard] → depends on writer
    quality-gate [gate] → depends on editor
    fixer [support]


  Install: cliq team install /Users/you/blog-pipeline
  Then:    cliq assemble blog-content-pipeline

Inspect and refine

Section titled “Inspect and refine”

Review what was generated:

Terminal window
cat team.yml
cat roles/writer.md

After installing, refine individual roles with targeted instructions:

Terminal window
cliq team install .


cliq builder improve blog-content-pipeline --role writer \
  --instruction "add more emphasis on storytelling and narrative structure"


cliq builder improve blog-content-pipeline --role quality-gate \
  --instruction "add checks for SEO best practices"

Find structural gaps:

Terminal window
cliq builder gaps blog-content-pipeline

Compose with existing teams

Section titled “Compose with existing teams”

Reference installed teams by @scope/name to embed them as sub-steps:

Terminal window
mkdir ci-pipeline && cd ci-pipeline
cliq builder generate -m "CI pipeline that runs @acme/security-audit then @acme/perf-suite, then writes a release report"

The builder resolves each referenced team, generates correct $(dirs.*) path stitching, and produces role-as-spec files that serve as requirement documents for each sub-team. See Builder — Composing Teams for details.

Assemble and run

Section titled “Assemble and run”
Terminal window
cliq team install .
cd my-project
cliq init
cliq assemble blog-content-pipeline
cliq req -m "Write a blog post about the future of AI agent coordination"
cliq run

Configuration

Section titled “Configuration”

Builder commands require an LLM provider configured in ~/.cliqrc/settings.json under the builder section. See Builder for configuration details.

When to use this path

Section titled “When to use this path”

You want a fast start with AI assistance and plan to refine iteratively. Builder-generated teams are good out of the box and great after a few rounds of improve and gaps. If you want full control over every file, see Build from Scratch.