EDD is how you prove tool calls. When the job is a product feature, the orchestrator still routes work through specialist roles: grilling, spec, TDD, cross-functional quality, audit, telemetry, and release. Language and framework profiles load on top of that once the stack is known.
sequenceDiagram
autonumber
participant O as orchestrator
participant G as grilling
participant S as spec
participant T as tdd
participant X as xfn
participant Sec as security
participant Arch as arch-drift
participant Tel as telemetry
participant R as release
O->>G: Stress-test idea and decision frontier
O->>S: BDD spec and acceptance criteria
O->>T: Inventory catalog and plan test impact
O->>X: Cross-functional quality matrix
O->>T: TDD short loop (gear 1 + gear 2)
O->>X: Green apply-row XFN suites
O->>Sec: Security and OWASP audit
O->>Arch: Hexagonal boundaries, no drift
O->>Tel: Map SLOs to OpenTelemetry
O->>R: Conventional PR title and handover1. **Grilling:** If the idea is still mushy, interview until the decision frontier is clear. 2. **Spec:** Gherkin and acceptance criteria, including cross-functional rows. 3. **TDD:** Inventory the behavior catalog, then gear 1 (domain) and gear 2 (thin adapters) in the same loop. EDD lives here when the change is a prompt or tool schema. 4. **XFN:** Green the apply rows (accessibility, load, security) or skip with a reason. 5. **Audit:** Security and architecture-drift checks, then pre-commit. 6. **Telemetry and release:** Map SLOs, update public docs if you touched them, ship with a conventional PR title.