Copy an Existing Team

If an existing team is structurally close to what you need — similar number of phases, similar gate placement, similar flow — copying it is the fastest path. You get a working foundation and only change what’s different.

Copy the team

cliq team copy @cliq/hello-world ./blog-pipeline

This creates ./blog-pipeline/ — a full copy of the team’s team.yml, roles/ directory, and any other files. The new team is independent; changes don’t affect the original.

You can copy any team you have access to in the registry:

cliq team copy @cliq/feature-dev-js ./my-dev-team
cliq team copy @local/my-experiment ./my-experiment-v2

To rewrite the scope in team.yml during the copy, pass an optional scope argument:

cliq team copy @cliq/hello-world ./blog-pipeline @myorg

What to change

Open ./blog-pipeline/team.yml and start adapting:

Rename phases — change planner to researcher, writer stays writer, reviewer becomes editor or quality-gate
Add or remove phases — insert new entries in workflow.phases with appropriate depends_on edges, or remove phases you don’t need
Rewrite roles — open each file in roles/ and rewrite the identity, responsibilities, boundaries, and workflow sections to match your new pipeline
Adjust gate checks — update the shell commands to validate the right things
Rename role files — if you renamed a phase, rename the matching file in roles/ (the file name must match the phase name)

Validate and test

After making changes, validate the structure:

cliq team validate blog-pipeline

Install the team, then assemble and run:

cliq team install ./blog-pipeline
cd my-project
cliq init
cliq assemble @local/blog-pipeline
cliq req -m "your requirement"
cliq run

When to use this path

The existing team’s phase structure — number of phases, gate placement, parallel branches — is close to what you need. If you’d be rewriting more than half the team, building from scratch or generating with Builder will be faster.