The Team Defines The Goal.
Not the orchestrator. The team writes the plan too — the orchestrator that produces a plan has already failed, and the protocol says so in those words.
Inside The IncredAgents Mod Pack
A panel of specialist voices — each with a lens the orchestrator doesn't have — researches, plans, and converges before anything reaches you. The orchestrator routes work and holds the process. It never touches the artifact.
The order
No goal definition. No research findings. No status paragraphs. A compact table — role, model, provider — and your approval. Then the team works.
Not the orchestrator. The team writes the plan too — the orchestrator that produces a plan has already failed, and the protocol says so in those words.
Advisor sees strategic risk. Builder catches implementation traps. Linter finds structural flaws. QA verifies against observable criteria. Kaizen audits every decision against the goal.
Plans reach you as a brief only after the team converges — you review, you approve, then execution begins without re-confirmation theater.
The guardrails
Every dispatch, completion, failure, and decision lands in a read-only audit trail — timestamped, structured, and out of the convergence vote entirely.
Session header on dispatch, timeline events as they happen, footer at the end. It never edits a file or makes a recommendation.
Different model families per role produce genuinely different lenses — blind spots in one architecture get caught by another.
One provider available? Separate instances with role-specific prompts preserve independent reasoning. The multi-lens chain survives the budget.
Get started
Ships in the mod pack. Pair it with Routing-Matrix to fill the lineup.
$ git clone https://github.com/MyAiFreedomSystems/incredagents.git
$ cd incredagents
$ python3 onboard.py
One installer wires in the whole mod pack and asks only for the keys each skill needs.
The next build gets a team that has to agree — before you see anything.
Get Moe-Build-Team On GitHub →