Home
Back to orbit
Me
Background & awards
Projects
Selected work
Articles
Latest writing
At a Glance
Snapshot & status
Agentic
AI pipeline
Sitecore
SitecoreAI with agents
Theme
Available
Autonomous Agent Organization

Three tracks,
one workspace.

Project development, research & competitive intelligence, and product management — all driven by specialized AI agents with structured handoffs and quality gates between every stage.

View DashboardView Projects
Agents
14
Parallel Tracks
3
Commands
14
Artifact Types
12
Architecture

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.

9
Dev Agents
2
Researchers
3
Product Managers
18
Commands
The Three Tracks

How the workspace is organized.

01Agents 00-08, 99

Project Development

Staged pipeline from raw idea to deployed code. Rubber Ducky brainstorm, PRD with adversarial review, architecture + ADRs, UI design with clickdummies, task breakdown with § 4c contracts, TDD enrichment, and slim-context implementation.

/prime/build-whole-feature/create-prd/challenge-prd/refine-implementation-plan/execute-implementation-plan/verify/qa
02Agents 10-11

Research & CI

Vendor-neutral technology intelligence and competitive analysis across four research lenses: release tracking, security monitoring, ecosystem trends, and community voice. One merged report per subject.

/release-the-minions
03Agents PM-S, PM-J, PM-C

Product Management

Technical PM evaluation of managed Sitecore repositories — SitecoreAI Starter, JSS monorepo, and Content SDK. Each PM specialization consumes upstream research and CI briefs, then assesses package maturity, migration pressure, and ecosystem alignment.

/release-the-minions
The Core Pipeline

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. Each output becomes the next input through structured handoffs.

Orbital view — CSS 3D component
00
Team LeadOrchestration & Gates
Agent 00Orchestration & Gates
Sequences specialist agents, validates handoffs between stages, and enforces quality gates. Low ceremony — stops bad artifacts before they propagate downstream.
02
Product ManagerPRD & Spec Review
Agent 02PRD & Spec Review
Writes testable specs from brain dumps, defends MVP scope, and runs adversarial 'pessimistic roast' sessions to stress-test requirements before they reach architecture.
04
Software ArchitectArchitecture & ADRs
Agent 04Architecture & ADRs
Converts PRDs into concrete technical blueprints with explicit Architecture Decision Records. Consequence-oriented — names trade-offs and checks for conflicts with existing decisions.
05
UI DesignerDesign Proposals & Clickdummies
Agent 05Design Proposals & Clickdummies
Produces 1-3 fundamentally divergent design directions with full rationale and self-contained HTML clickdummies for browser evaluation. Research-grounded aesthetics — asks constraints before designing, not after.
06
Lead DeveloperTask Breakdown
Agent 06Task Breakdown
Breaks epics into atomic tasks with stable IDs and the mandatory § 4c execution contract — seven subsections that give the Developer everything needed without opening other docs.
07
QA SpecialistTDD Enrichment
Agent 07TDD Enrichment
Embeds test-first discipline directly into the task breakdown before implementation starts. Edits tasks in-place, reorders for RED-GREEN-REFACTOR, ensures tests are behavioral.
08
DeveloperImplementation
Agent 08Implementation
Slim-context executor who receives only prd-minimal + enriched task breakdown. Implements exactly what was planned — stops and asks rather than compensating for ambiguous specs.
On-Demand Specialists

Called when needed.

Two agents that operate outside the core pipeline. They inject context at the start of a run — one surfaces hidden assumptions before planning begins, the other extracts structure from an existing site.

01
Rubber Ducky
Brainstorm & Discovery

Interrupt-first brainstorming facilitator that forces clarity through relentless questioning. Surfaces gaps, assumptions, and scope creep before they become costly.

Invoked via /do-rubber-ducky-session — standalone, pre-pipeline. Produces a brain-dump artifact that feeds into PRD creation.
99
Source Analyst
Source Discovery & Parity

Analyses reference URLs in greenfield mode (lightweight) or crawls a live site for full parity rebuild. Never invents content — labels everything as extracted or inferred.

Activated by /build-whole-feature when a URL is provided. Runs in greenfield (lightweight reference) or rebuild (full parity crawl) mode.
Development Track

The builders.

9 agents that take a raw idea through brainstorming, specification, architecture, design, planning, testing, and implementation. 7 form the core pipeline, 2 are on-demand specialists invoked when the context calls for them.

00

Team Lead

Orchestration & Gates

Sequences specialist agents, validates handoffs between stages, and enforces quality gates. Low ceremony — stops bad artifacts before they propagate downstream.

01

Rubber Ducky

Brainstorm & Discovery

Interrupt-first brainstorming facilitator that forces clarity through relentless questioning. Surfaces gaps, assumptions, and scope creep before they become costly.

02

Product Manager

PRD & Spec Review

Writes testable specs from brain dumps, defends MVP scope, and runs adversarial 'pessimistic roast' sessions to stress-test requirements before they reach architecture.

04

Software Architect

Architecture & ADRs

Converts PRDs into concrete technical blueprints with explicit Architecture Decision Records. Consequence-oriented — names trade-offs and checks for conflicts with existing decisions.

05

UI Designer

Design Proposals & Clickdummies

Produces 1-3 fundamentally divergent design directions with full rationale and self-contained HTML clickdummies for browser evaluation. Research-grounded aesthetics — asks constraints before designing, not after.

06

Lead Developer

Task Breakdown

Breaks epics into atomic tasks with stable IDs and the mandatory § 4c execution contract — seven subsections that give the Developer everything needed without opening other docs.

07

QA Specialist

TDD Enrichment

Embeds test-first discipline directly into the task breakdown before implementation starts. Edits tasks in-place, reorders for RED-GREEN-REFACTOR, ensures tests are behavioral.

08

Developer

Implementation

Slim-context executor who receives only prd-minimal + enriched task breakdown. Implements exactly what was planned — stops and asks rather than compensating for ambiguous specs.

99

Source Analyst

Source Discovery & Parity

Analyses reference URLs in greenfield mode (lightweight) or crawls a live site for full parity rebuild. Never invents content — labels everything as extracted or inferred.

Slim Context Chain
Later stages load only what they need. The Developer (08) receives prd-minimal + enriched task breakdown — never the full PRD, architecture, or UI specs. If the task breakdown's § 4c execution contract is incomplete, that's a planning gap to fix upstream, not a context gap for the implementer to fill.
Research & CI Track

The researchers.

2 specialists producing vendor-neutral intelligence briefs. The Research Specialist covers technology topics (Next.js, React, Vercel, Sitecore), while the CI Specialist profiles competitors (Adobe, Contentful, Optimizely, Storyblok). Both apply four shared lenses: release tracking, security monitoring, ecosystem trends, and community voice.

10

Research Specialist

Technology Intelligence

Produces vendor-neutral intelligence briefs across four research lenses: release tracking, security monitoring, ecosystem trends, and community voice. One merged report per technology topic.

11

CI Specialist

Competitive Analysis

Profiles competitors (Adobe, Contentful, Optimizely, Storyblok) against Sitecore with factual SWOT analysis, version tables, and ecosystem assessment. Supplier of downstream PM synthesis.

Product Management Track

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 prioritized task backlog with migration pressure, package maturity, and ecosystem alignment assessments.

PM-S

SCB Product Manager

SitecoreAI Starter Evaluation

Technical PM for the xmcloud-starter-js repository. Evaluates starter layout, rendering host assumptions, template maintenance, and alignment with current Sitecore direction.

PM-J

JSS Product Manager

JSS Monorepo Assessment

Technical PM for the JSS monorepo. Assesses package topology, peer dependencies, migration pressure, release channels, and developer friction across packages.

PM-C

Content SDK Product Manager

Content SDK Lifecycle

Technical PM for the Content SDK repository. Focuses on package maturity, scaffolding quality, docs alignment, and the JSS-to-Content-SDK lifecycle transition.

Sitecore Analysis

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.

SC
/analyze-sitecore-site
Site Intelligence Command

Extracts the content model from serialized YML items (templates, renderings, field definitions, headless variants), fetches live Experience Edge layout data for runtime placeholder trees and component keys, and produces paired analysis reports — a content model summary and content examples document that downstream agents use for component scaffolding and implementation.

Content Model
Templates, fields, renderings from serialized YML
Edge Layout
Live placeholder trees and componentName keys
Paired Reports
*-content-model.md + *-content-examples.md
Core Principle: Identity / Command Separation
Agent files define persona and expertise only — no task instructions, no output formats. Commands inject the task, input/output contracts, and handoff rules at runtime. The Product Manager can write a PRD, challenge a PRD, or revise a PRD — depending on which command invokes it and in what mode. This separation means any agent can be reused for different tasks without creating new agent files.
Explore the Framework
Interested?

Build your own agentic workflow

This framework is extensible — from greenfield apps to Sitecore Marketplace modules. The same agents adapt to any domain through command injection, not prompt rewrites.