Use Cases

cliq’s core primitives — roles, workflows, channels, gates — are domain-agnostic. Engineering is the flagship, but the same infrastructure powers any workflow where specialist agents need to collaborate. This page provides common workflow patters meant to demostrate to you the power of cliq to tackle any conceivable workflow task. Use these templates as inspiration to build your own teams for you specific needs. The Team Development section will show how to do that, showing you how cliq can enable you to unleash the full power of AI-driven workflows with a simple set of commands.

Feature Development (TDD)

Build a complete feature from a requirement — designed, tested, reviewed, with a PR ready to merge.

Role	Purpose
architect	Reads requirements, designs the system, defines interfaces and file structure
tester	Writes a comprehensive failing test suite (TDD red phase)
developer	Implements until all tests pass (TDD green phase)
reviewer	Gate — runs build and test checks, approves or routes back to developer

[architect] → [tester] → [developer] → [reviewer]

Add git-setup and git-finalize phases to automate branch creation and PR submission. Pair with Jira integration to pull requirements from tickets and update them on completion.

Bug Fix from a Ticket

Reproduce a bug with a test, fix it, verify nothing else breaks, and open a PR — all from a Jira ticket reference.

Role	Purpose
tester	Writes a failing test that reproduces the bug
developer	Fixes the code until the test passes
reviewer	Gate — runs the full test suite, approves or routes back

cliq req -s jira:BUG-456
cliq run

On completion, cliq can post a comment to the Jira ticket with the PR link. On escalation, it can transition the ticket to “Blocked” and notify Slack.

Product Discovery

Research the market, write a PRD, and produce UX specs — before anyone writes a line of code.

Role	Purpose
market-researcher	Analyzes the competitive landscape, user needs, and market gaps
product-manager	Writes a PRD with user stories and acceptance criteria
ux-designer	Produces user flows, component hierarchy, and interaction specs

[market-researcher] → [product-manager] → [ux-designer]

The output is a complete discovery package ready to hand off to an engineering team.

Full Product Lifecycle

From product thinking through implementation and documentation — a complete engineering deliverable.

Role	Purpose
product-manager	Writes PRD, user stories, and acceptance criteria
ux-designer	UX specs and interaction design (parallel with architect)
architect	System design, interfaces, and file structure (parallel with UX)
tester	Writes failing tests based on architecture and UX specs
developer	Implements until tests pass
reviewer	Gate — runs checks and approves or routes back
technical-writer	Produces API docs, user guides, and changelog

              ┌─→ [ux-designer] ──┐
[product-mgr] ┤                   ├→ [tester] → [developer] → [reviewer] → [tech-writer]
              └─→ [architect] ────┘

Fan-out and fan-in handle the parallel work. The tester waits for both design streams to complete.

Content Pipeline

Produce researched, edited, optimized content from a brief.

Role	Purpose
researcher	Gathers facts, sources, and background material
writer	Produces the draft from research and brief
editor	Gate — evaluates quality, routes back to writer if needed
seo-reviewer	Optimizes for search and readability

[researcher] → [writer] → [editor] → [seo-reviewer]

The editor is a gate with editorial checklist criteria. If the draft doesn’t meet the bar, it routes back to the writer with feedback.

Research and Analysis

Gather data, analyze it from multiple angles in parallel, and synthesize into a report.

Role	Purpose
data-gatherer	Collects raw data, sources, and reference material
analyst	Quantitative analysis, trends, and patterns
strategist	Strategic implications and recommendations
report-writer	Synthesizes all inputs into a cohesive report

                ┌─→ [analyst] ────┐
[data-gatherer] ┤                 ├→ [report-writer]
                └─→ [strategist] ─┘

The analyst and strategist run concurrently. The report writer waits for both to finish before synthesizing.

Legal Contract Review

Analyze a contract, flag risks, and produce a structured summary for decision-makers.

Role	Purpose
contract-parser	Extracts key clauses, dates, obligations, and defined terms
risk-analyst	Identifies unfavorable terms, liability exposure, and missing protections
compliance-checker	Gate — verifies against regulatory requirements and company policy
summary-writer	Produces an executive brief with flagged items and recommendations

[contract-parser] → [risk-analyst] → [compliance-checker] → [summary-writer]

The compliance checker is a gate — if the contract violates policy, it routes back to the risk analyst for deeper analysis before the summary is written.

Grant Proposal

Assemble a grant application from research objectives through budget justification.

Role	Purpose
literature-reviewer	Surveys prior work, identifies gaps, and establishes novelty
proposal-writer	Writes the narrative — objectives, methodology, expected outcomes
budget-planner	Produces a detailed budget with justifications
compliance-reviewer	Gate — checks formatting, page limits, required sections, and funder guidelines

[literature-reviewer] → [proposal-writer] → [budget-planner] → [compliance-reviewer]

Incident Post-Mortem

Turn a production incident into a structured post-mortem with timeline, root cause, and action items.

Role	Purpose
timeline-builder	Reconstructs the incident chronology from logs and alerts
root-cause-analyst	Identifies contributing factors and the root cause
action-planner	Proposes preventive measures with owners and deadlines
reviewer	Gate — ensures the post-mortem is blameless, complete, and actionable

[timeline-builder] → [root-cause-analyst] → [action-planner] → [reviewer]

Pull incident data from external sources using pull: entries — PagerDuty exports, Slack thread archives, or monitoring dashboards.

Onboarding Package

Generate a new-hire onboarding package tailored to a specific role and team.

Role	Purpose
role-analyst	Analyzes the job description, team structure, and expected responsibilities
curriculum-designer	Designs a 30/60/90-day learning plan with milestones
content-assembler	Gathers and organizes relevant docs, wiki links, and training materials
reviewer	Gate — ensures completeness, accuracy, and appropriate scope

[role-analyst] → [curriculum-designer] → [content-assembler] → [reviewer]

Security Audit

Run security-focused analysis on a codebase with specialized checks.

Role	Purpose
scanner	Static analysis, dependency audit, known vulnerability scan
security-analyst	Reviews findings, assesses risk, prioritizes issues
remediation-planner	Proposes fixes with effort estimates
security-reviewer	Gate — verifies the plan addresses all critical findings

[scanner] → [security-analyst] → [remediation-planner] → [security-reviewer]