Two Sitecore tracks, both in production.

Sitecore meets agentic. The same multi-agent pipeline that built this website — tuned for the Sitecore ecosystem. Two tracks live below, each with its own dedicated page. Pick the one that matches the work you have in front of you, or read both — they share the same operator-in-the-loop methodology underneath.

Both tracks are the same engine. Since the packs refactor they are not two branches of it either: a run answers three independent questions — platform (what you build on), method (where the spec comes from: greenfield or a parity clone of an existing site), and audience (who operates it: a developer, or a marketer on a guided flow) — and the answers compose rather than multiply. Twelve combinations, ten runnable, seven published as self-contained flows; the invalid ones are refused by name at resolution time. A platform pack supplies the domain — the skills, the scaffold, the definition of done, the release step — while the shared agents carry no platform knowledge at all and resolve a generated brief per run. Agents are identities, commands are tasks, packs are domains. Each track's page below spells out what changes when you turn each dial.