Player profile
ccswarm
An MIT-licensed Rust coding-agent workflow engine built around Sangha: Claude Code and Codex run plan, quorum assessment, implementation, review, and fix stages, with parallel workers and recorded run events.
Profile
Where it fits
ccswarm's Sangha workflow stages planning and quorum assessment before implementation, review, and fixes. Flow YAML and recorded run events make the declared process inspectable and repeatable.
It belongs in Parallel Coding-Agent Runners because its built-in team flow runs frontend and backend work in parallel before supervisor review, while team-dynamic uses a leader with workers. The documented acceptance and permission limitations mean a quorum or review result must not be treated as an independently enforced safety or build guarantee.
Builder web analytics
Measure projects built with ccswarm
Separately configured analytics can measure a deployed change after a ccswarm workflow and independent checks have finished.
This is an optional measurement workflow, not a native ccswarm integration. Configure product tracking and analytics access separately; approval markers and recorded run events do not prove product outcomes or replace required checks.
First loop to measure
- workers implement a change and reviewers assess it
- the operator runs required checks separately and deploys the reviewed result
- the instrumented product reports configured events
- an agent with separately configured analytics access reads outcomes for the next task
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including deployed page, signup, activation event, or funnel step. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which deployed page, signup, activation event, or funnel step moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.