Questions about adopting Cloverleaf

How is Cloverleaf different from Scrum?

Scrum assumes humans are the slow part of building software. Cloverleaf assumes AI is the primary author and humans are the slow part of judgment. The result is a different bottleneck and a different optimisation: Cloverleaf shifts human attention upstream into strategy and review, where the leverage now lives.

How is Cloverleaf different from Shape Up?

Shape Up keeps humans implementing during the cycle and uses appetites as a soft cap. Cloverleaf removes humans from implementation entirely (agents do that) and uses gates as hard caps on strategy and merge.

Can a single developer use Cloverleaf?

Yes. The 7 agents are recommended roles, not staffing. A solo dev can switch personas in a single Claude session and still get the structural benefits of fresh-eyes review and typed failure handling.

What about teams that aren't using AI yet?

Cloverleaf is specifically for teams where AI is the primary code author. If your team writes most code by hand, Scrum or Shape Up will fit better.

Is the methodology stable?

Standard v0.3.0 (this version). The architecture (two tracks, 4 work items, 7 agents) is settled. Some details may evolve based on real-team feedback.

Is there a reference implementation?

Yes — @cloverleaf/reference-impl on npm. It implements the Delivery track as Claude Code skills (Implementer, Documenter, Reviewer, UI Reviewer, QA) and dispatches them via the orchestrator /cloverleaf-run. The Discovery track (Plan, Researcher) is still stubbed; a v0.4 release is planned.

How do I cite Cloverleaf?

Cite the live guide at https://cloverleaf-org.github.io/cloverleaf/ and pin to the Standard version shown in the footer (currently v0.3.0). A DOI may follow.