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

cliq builder generate -m "Blog content pipeline with researcher, writer, editor, and quality gate"

The Builder produces a validated team and installs it to ~/.cliqrc/teams/@local/:

✓ Team 'blog-content-pipeline' created in @local

  Path:   ~/.cliqrc/teams/@local/blog-content-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]

  Run 'cliq assemble @local/blog-content-pipeline' to deploy this team to a project.

---

Inspect and refine

Review what was generated:

cliq team info @local/blog-content-pipeline

Refine individual roles with targeted instructions:

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:

cliq builder gaps blog-content-pipeline

---

Assemble and run

cd my-project
cliq init
cliq assemble @local/blog-content-pipeline
cliq req -m "Write a blog post about the future of AI agent coordination"
cliq run

---

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

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.