The agents

A small studio that never sleeps. Three core agents run every cycle; discovery and delivery bookend it as optional modules. One conductor can run the whole thing for you.

One command that orchestrates the cycle and adapts to your level — guided or terse.

CONDUCTOR — /pds (entry point)

Preps interviews, synthesizes research, restitutes findings — before DIRECTION.

EVE — Discovery (optional)

Brief half writes the direction (gate ①); build half implements it (PRODUIRE).

BOB — Builder & Quality Director

Writes the scope after the direction, against it (CADRE, gate ②) — Standard/System only.

RAY — Architect & Strategist

Two verdicts, never averaged: a /20 conformance score, and the designer’s binary call.

ANALYZER — Product QA & CX

Runs the deployment checklist once both verdicts clear.

SHIP — Delivery (optional)

How they hand off


(eve)              recherche, optionnel — problem brief
   ↓
bob --brief        DIRECTION ....................... ⏸ gate ①
   ↓
(ray)              CADRE — Standard/System only ..... ⏸ gate ②
   ↓
bob --build        PRODUIRE — code, or Figma via design-workflow
   ↓
(design-handoff)   HANDOFF, optionnel — Figma → dev spec
   ↓
analyzer           JUGER — conformance + direction ... ⏸ gate ③
   ↓
(ship)             delivery, optionnel

Parenthesized steps are optional and never gate the cycle. Each agent reads a defined set of inputs and produces a defined artifact. The learnings ANALYZER writes feed back into RAY, so every cycle is sharper than the last.