Build an agent team for your project.

Give plyk a project goal. Review the proposed roles, choose models available in your tool, and set a usage limit before work begins.

Get plyk Try the team builder
You approve the direction. Main coordinates the team.
  • S / Secondary / Architecture
  • U / Support / Implementation
  • A / Aligner / Verification

Supported coding hosts

  • Codex
  • Claude Code
  • Antigravity
  • Kiro
  • LM Studio

Team structure

Give each role a defined job.

The Main Pivot proposes only the roles the assignment needs. You approve the team. Each worker gets a bounded scope and returns evidence and unresolved limits.

OP Human

Organic Pivot

Sets the goal, owns the project, and approves consequential decisions.

MP Coordinator

Main Pivot

Plans the assignment, selects roles and models, tracks ownership, and combines results.

SE Up to 3

Secondary Pivot

Handles architecture, complex implementation, and technical investigations.

SP Up to 3

Support Pivot

Builds interfaces and routine features within assigned files or modules.

AP Up to 3

Aligner Pivot

Runs DevOps, QA, release verification, and operational checks.

Optional roles
MS

Messenger

Moves approved context between roles when the host exposes the required controls.

IE

Independent evaluator

Checks results independently from the role that produced them.

Setup and control

plyk checks the host before it creates the team.

It uses native definitions and chat controls only when the host exposes them. A saved definition does not prove that an agent is running or that a project chat exists.

01

Inspect capabilities first

plyk records which agent, chat, model, and tool controls the current host exposes.

02

Keep assignments bounded

Each role receives owned paths, constraints, required checks, and a stopping point.

03

Evidence at handoff

Workers report changed paths, checks run, failures, and unresolved limits.

04

Choose current models

plyk recommends models available in the host. You can accept or replace each choice.

05

Set the usage limit

plyk reads plan and allowance data when the host exposes it. Otherwise, it asks you for the project limit.

Platform setup

Choose your coding tool.

See the setup format and chat support for each tool.

Native definitions Codex

Uses project agent definitions when Codex exposes them.

plyk writes project-scoped agent definitions. It creates visible project chats only when the current Codex session exposes native chat controls.

Team format
Native definitions
Visible chats
Native control required
Fallback
Portable role prompts

Support varies by version and environment. plyk checks the available controls during setup.

Get plyk

Choose your tool. Install in your project.

Download the package, unzip it, then run the installer for your coding tool.

Loading download packages...

Usage estimates

Set a project limit before work starts.

plyk reads plan and allowance information when the host exposes it. If it cannot, it asks you for the limit to use. The Main Pivot reviews scope at 70% and stops discretionary work at 90%.

Project estimate70% scope review
Start90% stop discretionary work

Provider meters may include other projects. These estimates do not enforce a billing cap.

Team builder

Describe the work. Edit the proposed team.

The preview detects explicit role phrases in your text. It runs locally and does not use a model.

Mention roles such as lead engineer, frontend, DevOps, QA, messenger, or evaluator.

Your text stays in this page. It is not stored or sent anywhere.

Preview

Proposed team

Preview only. Detection is approximate. Select any role to edit it.

Enter a goal to build a preview.

No team yet Type a goal or use the example.
Generated invocation 
Generated invocation will appear here.

Model names are user supplied. Verify availability in the selected tool before work starts.