How it works

From install to export in six steps.

Install teams like packages, compose them into a workspace, and export to the coding assistant you already use.

Create a workspace

A workspace represents one project or company. Everything you install lives here — teams, skills, rules, knowledge, and workflows.

One workspace per product or org
Independent from other projects
Ready for installs and exports

Install AI teams

Pick the roles your AI should become — not a giant prompt, a structured organization.

Engineering, Product, Marketing, Finance
Sales, Support, Security, DevOps, Legal, QA
Each team brings identity, responsibilities, and standards

Add skills, rules & knowledge

Layer reusable expertise and non-negotiable standards onto your teams.

Skills: OAuth, Cloudflare, Laravel, payments, SEO
Rules: auth required, tests on PRs, thin controllers
Knowledge packs: framework and technology references

Attach a workflow

Tell the AI how work should move — so it doesn’t jump straight to code.

Requirement → Architecture → Planning
Implementation → Testing → Review
Documentation → Release

Compose automatically

AgenticTeam assembles your installed packages into one coherent organization. You never hand-merge prompt files.

Teams + skills + rules + knowledge + workflow
Dependencies resolve with the install
Versions stay pinned until you upgrade

Export to your coding assistant

Generate the right config for the tool you use today — switch tools tomorrow without rewriting context.

Cursor, Claude Code, Codex, Gemini CLI
Continue, Aider, Windsurf, and future tools
agentic export cursor — done

Example flow

# Build an AI organization
$ agentic init
$ agentic install engineering-team
$ agentic install marketing-team
$ agentic install finance-team
$ agentic install oauth
$ agentic install feature-delivery
$ agentic export cursor
$ agentic sync