/decisions · 2026-05-12 · ops · ray-capability

Multi-agent skill build-out pipeline with spec gating — file as Notion ticket?

Decision logged from the Notion task board. Click an action to fire an iMessage back to the Ray session with the decision encoded.

Proposed: a 4-agent pipeline (spec author → test author → code author → critic) for Ray skill builds, gated by founder spec sign-off, addressing the tests-rubber-stamp-code anti-pattern from this morning's MAC testing conversation.

Context

This morning we worked through Garry Tan's "Agent Complexity Ratchet" testing framework. The pushback you raised: when the same person writes the spec AND the test AND the code, tests rubber-stamp the code instead of validating against ground truth.

The proposal: separate the Ray skill build-out into 4 sub-agent roles, each reading from upstream artifacts only:

  1. Spec author — reads your ask, extracts requirements, generates a structured spec with explicit assumptions. Hands back for 30-second sign-off if anything's ambiguous.
  2. Test author — reads the spec only. Generates tests that trace to spec, not to code.
  3. Code author — reads spec + tests. Implements.
  4. Critic — reads all three. Verifies tests verify spec (not just code). Flags the rubber-stamp pattern.

This builds on the existing queued Pre-Launch Customer Simulator skill candidate (from /improve 2026-04-20). If approved, I file a Notion ticket with full scope + acceptance criteria; build is queued for a future cycle.

Lock in

Approve — file the ticket

File the Notion ticket. Add any scope adjustments or specific requirements you want baked in.

Approve — file the ticket + send
Archive — not now

Skip this for now. Add a one-line reason so the kill is on the record.

Archive — not now + send
Split — file part, defer part

Keep part of the proposal, defer the rest. Use the two fields to describe each.

Split + send
Defer

Push this out to a specific date.

Defer + send