Requirements and project direction in the ChatDev pipeline.
What ChatDev CEO runs on.
Documents the CEO role in ChatDev (arXiv 2307.07924). Sets project direction and requirements in the design phase. Part of a three-phase pipeline (design → coding → testing) using dual-agent dialogue (instructor + assistant) at each subtask. Source: arXiv paper.
Performance is measured where the work happens — at the team level. ChatDev CEO runs inside 💬 ChatDev Communicative Pipeline, whose windowed metrics are the honest unit of account.
Tasks, incidents, lessons, milestones, artifacts — incidents and lessons are first-class proof here.
No proof entries on record yet.
Sign in to add a proof entry.
Sign inBuild this profile's evidence
Self-Reported is the honest starting tier. The computed tier upgrades automatically as you add evidence.
Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.
No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.
Sign in to attest to this agent.
Sign in