The Team.
Project development, research & competitive intelligence, and product management — all driven by specialized AI agents with structured handoffs and quality gates between every stage.
Three parallel tracks, zero overlap.
Each track has its own agents, commands, and output artifacts. They share a common orchestration layer and agent identity model but run independently — you can launch a research cycle while a project pipeline is mid-execution.
How the workspace is organized.
From idea to production.
Seven agents in sequence: Team Lead orchestrates, Product Manager specs, Architect designs, UI Designer proposes, Lead Developer breaks down, QA enriches, Developer implements. A final /ship stage closes the loop with a release checklist. Each output becomes the next input through structured handoffs.
Called when needed.
Four agents that operate outside the linear core pipeline. They are pulled in when the context calls for them — to surface hidden assumptions before planning, ground a fuzzy claim mid-conversation, extract structure from an existing site, or run a heavy documentation pass.
The builders.
11 agents that take a raw idea through brainstorming, specification, architecture, design, planning, testing, implementation, and shipping. 7 form the linear core pipeline; 4 are on-demand specialists — Rubber Ducky, Research Sidecar, Doc Writer, and Source Analyst — invoked when the context calls for them.
The researchers.
3 specialists producing vendor-neutral intelligence briefs. The Research Specialist covers technology topics across the modern web stack, the CI Specialist profiles competing platforms with factual SWOT analysis, and the DevX Specialist distils a developer-experience industry trend brief. All apply four shared lenses: release tracking, security monitoring, ecosystem trends, and community voice — and the track now outputs strategic initiatives, not a task backlog.
The product managers.
3 specialized PMs that evaluate managed Sitecore repositories as product surfaces. Each consumes upstream research and CI briefs, inspects the actual repo, and produces a register of initiatives — JPD-altitude bets gated by altitude and control — rather than a granular task backlog. A chosen initiative is promoted into delivery via /create-prd or /create-frd.
Deep-dive into any Sitecore site.
A dedicated command that combines content model extraction, live Edge layout analysis, and component mapping into a comprehensive site profile — feeding directly into project development or research workflows.
Skills trained by shipping real apps.
The Marketplace SDK skill files in this workspace weren't written from documentation alone — they were validated by building real apps against them. Nine consecutive dogfood runs (plus a dry run) were used to surface gaps, fix incorrect assumptions, and battle-test every code pattern before it was committed as a skill.
Where the dogfood patches live now.
The 46 skill files trained by the dogfood loop don't ship inside this repo anymore. They live in a separate, auto-discoverable Claude Code plugin and a Cursor / Codex / Cline / Gemini CLI distribution — installed once per environment, then invoked by name from any agent.
Go deeper into how this gets shipped
Methodologies and case studies show the agentic pipeline in motion — the patterns the agents converge on, and what that produced when run end-to-end against real Sitecore tenants.
Build your own agentic workflow
This framework is extensible — from greenfield apps to Sitecore Marketplace modules and Content SDK head apps. The same agents adapt to any domain through command injection, not prompt rewrites.